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
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: 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
