Re: lmtp sockets and sieve / duplicate suppression
On Thu, Sep 06, Scott Russell wrote: > Question about using lmtp sockets vs using deliver. Does using lmtp sockets > on cyrus at all take away my ability to use sieve scripts or duplicate > suppression? No, of course not. -- With best regards, Carsten Hoeger SuSE, The Linux Experts, http://www.suse.com Key fingerprint = E3B6 7FDB 4800 0F22 DC09 EB2B 7988 B6A8 6691 C94A PGP signature
migrate exchange mailbox to cyrus mailbox
Dear all, Is there any method/tools to migrate the mailbox in Exchange Server to Cyrus server? Could anyone share your experience? Thanks and regards, Boris
Re: migrate exchange mailbox to cyrus mailbox
[EMAIL PROTECTED] wrote: > Is there any method/tools to migrate the mailbox in Exchange Server to Cyrus > server? Could anyone share your experience? > I haven't done this myself, but it wouldn't be hard to write a Perl script that uses Exchange's COM interface to enumerate users, folders, and messages on an Exchange Server (using the OLE module that comes with ActivePerl) and move them to Cyrus (using the Cyrus admin module that comes with IMAPd). I don't have access to an Exchange server at the moment so I can't try any example code.
Re: migrate exchange mailbox to cyrus mailbox
Hi You can make a perl script which read messages (in exange) and append this messages in user's cyrus box. At 19:03 07/09/01 +0800, [EMAIL PROTECTED] a écrit: >Dear all, > >Is there any method/tools to migrate the mailbox in Exchange Server to Cyrus >server? Could anyone share your experience? > > >Thanks and regards, >Boris -- Julien Marchal -- Email : [EMAIL PROTECTED] Université NANCY 2 - C.R.I. 13, Rue Michel Ney CO 75 - 54037 Nancy Cédex
Re: Malboxes with dots - Reprise
Sherpya wrote: > > I've succesfully installed and configured cyrus hiersep-r2 version from Ken > Murchison version 2.0.15, IMAP works ok, POP3 does not auth me... any idea? > POP3 says Invalid login How is Cyrus configured -- altnamespace? unixhiersep? What is the userid that you are trying to use? What login mech -- USER/PASS, APOP, or AUTH? Ken -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: lmtp sockets and sieve / duplicate suppression
--On Friday, September 07, 2001 9:11 AM +0200 Carsten Hoeger <[EMAIL PROTECTED]> wrote: > On Thu, Sep 06, Scott Russell wrote: > >> Question about using lmtp sockets vs using deliver. Does using lmtp >> sockets on cyrus at all take away my ability to use sieve scripts or >> duplicate suppression? > > No, of course not. Maybe just a *little* more description would help :-> Anyways, deliver is nothing more than a wrapper that connects to the LMTP socket itself. The deliver program doesn't actually do the delivery anymore. So, the effect is the same... Scott -- +-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-+ Scott W. Adkinshttp://www.cns.ohiou.edu/~sadkins/ UNIX Systems Engineer mailto:[EMAIL PROTECTED] ICQ 7626282 Work (740)593-9478 Fax (740)593-1944 +-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-+ CNS, HDL Center, Suite 301, Ohio University, Athens, OH 45701-2979
Re: lmtp sockets and sieve / duplicate suppression
On Fri, Sep 07, 2001 at 10:24:59AM -0400, Scott Adkins wrote: > --On Friday, September 07, 2001 9:11 AM +0200 Carsten Hoeger > <[EMAIL PROTECTED]> wrote: > > > On Thu, Sep 06, Scott Russell wrote: > > > >> Question about using lmtp sockets vs using deliver. Does using lmtp > >> sockets on cyrus at all take away my ability to use sieve scripts or > >> duplicate suppression? > > > > No, of course not. > > Maybe just a *little* more description would help :-> Anyways, deliver > is nothing more than a wrapper that connects to the LMTP socket itself. > The deliver program doesn't actually do the delivery anymore. So, the > effect is the same... This is what I've read here on the lists myself. What prompted me to ask was the switches that deliver takes. For example deliver takes a switch to turn off duplicate email suppression. Obviously I cannot pass switches to my lmtp socket... So if deliver is nothing but a lmtp wrapper and it's no different than doing direct lmtp delivery why does deliver take switches for delivery control? Also, will the deliver wrapper be dropped from future releases of cyrus imapd? Thanks much. -- Regards, Scott Russell ([EMAIL PROTECTED]) Linux Technology Center, System Admin, RHCE. T/L 441-9289 / External 919-543-9289 http://bzimage.raleigh.ibm.com/webcam
alternate path for cyrus.conf
I am looking to run more than one master process on a machine, and I am curious of the reasons why I would not want to do this. The reason that I want to do this is becuase I will be running cyrus in an failover configuration. Greg
Re: lmtp sockets and sieve / duplicate suppression
Scott Russell wrote: > > On Fri, Sep 07, 2001 at 10:24:59AM -0400, Scott Adkins wrote: > > --On Friday, September 07, 2001 9:11 AM +0200 Carsten Hoeger > > <[EMAIL PROTECTED]> wrote: > > > > > On Thu, Sep 06, Scott Russell wrote: > > > > > >> Question about using lmtp sockets vs using deliver. Does using lmtp > > >> sockets on cyrus at all take away my ability to use sieve scripts or > > >> duplicate suppression? > > > > > > No, of course not. > > > > Maybe just a *little* more description would help :-> Anyways, deliver > > is nothing more than a wrapper that connects to the LMTP socket itself. > > The deliver program doesn't actually do the delivery anymore. So, the > > effect is the same... > > This is what I've read here on the lists myself. What prompted me to ask was > the switches that deliver takes. For example deliver takes a switch to turn > off duplicate email suppression. Not any more (it accepts it, but it doesn't do anything). > Obviously I cannot pass switches to my lmtp > socket... Well... See http://www.imc.org/draft-murchison-lmtp-ignorequota This is how the -q option is implemented. This _might_ change to a general delivery options method in the future, ie "RCPT TO:<[EMAIL PROTECTED]> OPTIONS=qae" which would ignore the quota, ignore the ACL and turn off duplicate supression. > So if deliver is nothing but a lmtp wrapper and it's no different than doing > direct lmtp delivery why does deliver take switches for delivery control? See above. > Also, will the deliver wrapper be dropped from future releases of cyrus imapd? If/when all MTAs support LMTP, it _might_ go away. But, it would still have value for scripting, etc. Ken -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: lmtp sockets and sieve / duplicate suppression
--On Friday, September 07, 2001 11:01 AM -0400 Scott Russell <[EMAIL PROTECTED]> wrote: > On Fri, Sep 07, 2001 at 10:24:59AM -0400, Scott Adkins wrote: >> --On Friday, September 07, 2001 9:11 AM +0200 Carsten Hoeger >> <[EMAIL PROTECTED]> wrote: >> >> > On Thu, Sep 06, Scott Russell wrote: >> > >> >> Question about using lmtp sockets vs using deliver. Does using lmtp >> >> sockets on cyrus at all take away my ability to use sieve scripts or >> >> duplicate suppression? >> > >> > No, of course not. >> >> Maybe just a *little* more description would help :-> Anyways, deliver >> is nothing more than a wrapper that connects to the LMTP socket itself. >> The deliver program doesn't actually do the delivery anymore. So, the >> effect is the same... > > This is what I've read here on the lists myself. What prompted me to ask > was the switches that deliver takes. For example deliver takes a switch > to turn off duplicate email suppression. Obviously I cannot pass switches > to my lmtp socket... > > So if deliver is nothing but a lmtp wrapper and it's no different than > doing direct lmtp delivery why does deliver take switches for delivery > control? Also, will the deliver wrapper be dropped from future releases > of cyrus imapd? Ah, okay. Actually, doesn't deliver take a switch to turn *on* duplicate email suppression (the -e switch)? Anyways, the -e option is depracated and now actually does nothing. Duplicate delivery suppression is on by default. As far as I can tell, there is no way to turn off the use of duplicate delivery suppresion, unless you modify the source code. As for the removal of the deliver wrapper in a future version, I am not sure, but I hope not. Deliver is useful if you need some means of deliverying a message to a user's mailbox from a shell script or similar program. For example, we had one of our imap partitions corrupt last week. We were able to restore from tape, but there was the time period from when the backup was made and when the system went down that were not backed up. This makes sense when you think of backups being done only at nights. We were able to salvage our disk with a utility that restored most of the files onto some backup partition we had. Using deliver, we were able to "re-deliver" all the messages between the backup time and crash time, so the users actually didn't lose any mail... it was just severely delayed. In any the case, I think there will always be a good use for deliver. As far as duplicate delivery suppression goes, I think we need a protocol expansion or something that allows it to be done, much like how the ignore quota feature works. I wonder if that would be possible? Scott -- +-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-+ Scott W. Adkinshttp://www.cns.ohiou.edu/~sadkins/ UNIX Systems Engineer mailto:[EMAIL PROTECTED] ICQ 7626282 Work (740)593-9478 Fax (740)593-1944 +-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-+ CNS, HDL Center, Suite 301, Ohio University, Athens, OH 45701-2979
Re: lmtp sockets and sieve / duplicate suppression
Date: Fri, 07 Sep 2001 12:11:43 -0400 From: Scott Adkins <[EMAIL PROTECTED]> Actually, doesn't deliver take a switch to turn *on* duplicate email suppression (the -e switch)? Anyways, the -e option is depracated and now actually does nothing. Duplicate delivery suppression is on by default. As far as I can tell, there is no way to turn off the use of duplicate delivery suppresion, unless you modify the source code. The main reason that it isn't an easy switch any more is Sieve. Sieve depends on the duplicate delivery suppression to avoid mail loops and the vacation functionality. Turning off both duplicate delivery suppression and Sieve is trivial. Turning off duplicate delivery suppression and leaving Sieve on is somewhat trickier if you want to avoid the mail loops. Larry
Re: limit of file descriptors
linux 2.0 and 2.2 have a FD limit ~512, this can be bumped up to 4092 with a source code edit, but cannot be pushed above that. 2.4 defaults to a much larger number (based on ram I think, on my 512M machines it's 8K) and can be bumped up to 32K or 64K (don't remember which at the moment) in a boot script David Lang On Thu, 6 Sep 2001, Jeremy Howard wrote: > Date: Thu, 6 Sep 2001 22:08:50 +1000 > From: Jeremy Howard <[EMAIL PROTECTED]> > To: Lawrence Greenfield <[EMAIL PROTECTED]>, > Horst Lederhaas <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > Subject: Re: limit of file descriptors > > Lawrence Greenfield wrote: > >From: "Jeremy Howard" <[EMAIL PROTECTED]> > >Date: Sat, 25 Aug 2001 08:15:42 +1000 > > > >Lawrence Greenfield wrote: > >> This message is usually harmless. > >> > >> Some systems limit how many file descriptors a process can use, and > >> the 'master' process tries bumping it up to be infinite. If it > fails, > >> it usually means that there's no default limit. > >> > >I too get this message, under Linux kernel 2.4.8. But I'm pretty sure > that > >Linux has an FD limit (1024 FDs according to `ulimit -a`). Do I have to > do > >something special to let Cyrus increase FDs under Linux? > > > > As long as root invokes master, there shouldn't be anything else. > > > Strange... I am on linux kernel 2.2.19 and root is invoking master. But I'm > still getting this error. I'm running 2.0.16. > > It's no big deal yet because I'm not hitting the limit, but I'm curious > now... What else could be causing the problem? How should I go about > debugging this one? > >
Re: lmtp sockets and sieve / duplicate suppression
Scott Russell wrote: > > > > > >> Question about using lmtp sockets vs using deliver. Does using lmtp > > > > >> sockets on cyrus at all take away my ability to use sieve scripts or > > > > >> duplicate suppression? > > > > > > > > > Maybe just a *little* more description would help :-> Anyways, deliver > > > > is nothing more than a wrapper that connects to the LMTP socket itself. > > > > The deliver program doesn't actually do the delivery anymore. So, the > > > > effect is the same... > > > > > > This is what I've read here on the lists myself. What prompted me to ask was > > > the switches that deliver takes. For example deliver takes a switch to turn > > > off duplicate email suppression. > > > > Not any more (it accepts it, but it doesn't do anything). > > > > > Obviously I cannot pass switches to my lmtp > > > socket... > > > > Well... See http://www.imc.org/draft-murchison-lmtp-ignorequota > > > > This is how the -q option is implemented. This _might_ change to a > > general delivery options method in the future, ie "RCPT > > TO:<[EMAIL PROTECTED]> OPTIONS=qae" which would ignore the quota, ignore > > the ACL and turn off duplicate supression. > > Thanks for the RFC reference Ken. Am I correct in inffering that Cyrus-IMAPd > 2.0.16 follows this? Yes -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: lmtp sockets and sieve / duplicate suppression
> > > >> Question about using lmtp sockets vs using deliver. Does using lmtp > > > >> sockets on cyrus at all take away my ability to use sieve scripts or > > > >> duplicate suppression? > > > > > > > Maybe just a *little* more description would help :-> Anyways, deliver > > > is nothing more than a wrapper that connects to the LMTP socket itself. > > > The deliver program doesn't actually do the delivery anymore. So, the > > > effect is the same... > > > > This is what I've read here on the lists myself. What prompted me to ask was > > the switches that deliver takes. For example deliver takes a switch to turn > > off duplicate email suppression. > > Not any more (it accepts it, but it doesn't do anything). > > > Obviously I cannot pass switches to my lmtp > > socket... > > Well... See http://www.imc.org/draft-murchison-lmtp-ignorequota > > This is how the -q option is implemented. This _might_ change to a > general delivery options method in the future, ie "RCPT > TO:<[EMAIL PROTECTED]> OPTIONS=qae" which would ignore the quota, ignore > the ACL and turn off duplicate supression. Thanks for the RFC reference Ken. Am I correct in inffering that Cyrus-IMAPd 2.0.16 follows this? -- Regards, Scott Russell ([EMAIL PROTECTED]) Linux Technology Center, System Admin, RHCE. T/L 441-9289 / External 919-543-9289 http://bzimage.raleigh.ibm.com/webcam
User unknown errors
Hey everyone, I have Cyrus Imap installed and working witht he latest sasl, BerkeleyDB and Sendmail. I am having a problem though. When a message is sent to a user on the system I get a unknown user error from sendmail. At least I think it is a sendmail error. The full error is like this : [EMAIL PROTECTED] User Unkown. The user has a mailbox, I can login to the imap server with the user and create mailboxes, etc.. but when it comes to delivering mail to the mailboxes it fails somewhere between Sendmail and Cyrus. Any ideas? thanks in advance Benjamin
Quota root problems
Good Afternoon! I am having very weird behavior out of my Cyrus 2.0.7 quota. On user mailboxes that were upgraded, everything seems to be okay. But on mailboxes created after, I get the following error: New Account: > lq user.mpill STORAGE 0/8000 (0%) > setquota user.mpill 9000 > lqr user.mpill NO QUOTA ROOTS old account: > lqr user.rsanna user.rsanna STORAGE 20902/3 (69%) any suggestions?
RE: Quota root problems
I have noticed the new accounts do not have a cyrus.seen file in the mailbox.How can I force this? quota -f is broken... -Original Message- From: Kiarna Boyd [SMTP:[EMAIL PROTECTED]] Sent: Friday, September 07, 2001 2:10 PM To: [EMAIL PROTECTED] Subject:Quota root problems Good Afternoon! I am having very weird behavior out of my Cyrus 2.0.7 quota. On user mailboxes that were upgraded, everything seems to be okay. But on mailboxes created after, I get the following error: New Account: > lq user.mpill STORAGE 0/8000 (0%) > setquota user.mpill 9000 > lqr user.mpill NO QUOTA ROOTS old account: > lqr user.rsanna user.rsanna STORAGE 20902/3 (69%) any suggestions?
imspd via stunnel?
Has anybody gotten imspd to work via stunnel? Without it can connect just fine. With it, get server identifier string, but then it hangs and doesn't respond to input -- Amos
No Subject
Title:
Re: imspd via stunnel?
Funny little gotcha with IMSP. It requires a CR/LF over stunnel, which doesn't always get there if you're using openssl to test it. To test it correctly, try "openssl s_client -crlf -connect imsp.somewhere.com:imsps" or whatever. If you're not using openssl to test it, chances are you're running into the same CR/LF problem, because that's exactly the behavior that we saw when we first tried it out. Good luck, Michael Bacon Systems Administration Duke University Amos Gouaux wrote: > Has anybody gotten imspd to work via stunnel? Without it can > connect just fine. With it, get server identifier string, but then > it hangs and doesn't respond to input > > -- > Amos
Re: imspd via stunnel?
> On Fri, 07 Sep 2001 19:07:28 -0400, > Michael T Bacon <[EMAIL PROTECTED]> (mtb) writes: mtb> correctly, try "openssl s_client -crlf -connect mtb> imsp.somewhere.com:imsps" or whatever. If you're not using openssl to mtb> test it, chances are you're running into the same CR/LF problem, because that's exactly it! Thanks. This was driving me nuts. I don't know if the person got it resolved or not, but looking in the archive I noticed someone asking about pwcheck with imspd. In case that's still an unresolved issue, I discovered that you need to have: /usr/local/lib/sasl/imspd.conf (or something as such depending on how things are compiled) containing: pwcheck_method: saslauthd (or change that to pwcheck if you're using that.) -- Amos
Question About LMTP-Auth
Excuse me if this has been asked before... I have configured sendmail to do unix domain socket lmtp calls. I then tested the email (mail -v account) and got the error message in syslog saying that I didn't auth and sendmail couldn't read /etc/mail/auth-info. So, I assumed it didn't work... however, the mail still went through. When I did add the auth info to auth-info, it worked fine.. no errors The error messages I received (after I entered data into auth-info... it was the wrong username/pass, but the mail still went through!).. Sep 7 19:43:09 mail1 lmtpd[1017]: badlogin: [unix socket] PLAIN authentication failure [unable to find match for user] The question is, why did it say I couldn't authenticate with the unix socket and still let the mail through? It seems that despite the authentication failure, it still works. Sendmail is compiled with STARTTLS and SASL Cyrus is compiled with SASL Thanks. -Ray
