On Thu, Dec 13, 2001 at 11:21:14AM -0500, Ken Murchison wrote: > > [EMAIL PROTECTED] wrote: > > > > We are running Cyrus IMAP4 v2.1.0pre, from a CVS of a month or so ago. > > Some users have sieve scripts that have two `redirect' commands, > > one specifying another e-mail address, and one specifying their own > > e-mail address. Their intention is to forward a copy of the mail > > and also deliver a copy to their INBOX. However, the second copy > > disappears. > > > > Apparently, Cyrus sieve re-mails both copies, but when the copy > > addressed to the original address is re-delivered, the duplicate > > supression mechanism discards it. > > How would we determine that they are redirecting to themselves? You'd > end up getting into the 'vacation' problem of knowing all of the user's > addresses and aliases.
Well, if the redirect address is the same as the envelope recipient, sieve could take a shortcut and just perform a `keep' operation. I realize that this would not prevent all mail loops, but it covers the most common case. Sendmail with .forward files handles this case correctly. > I think the users should be educated as to what is happening and on how > to use Sieve correctly. Isn't this kind of like walking to the post > office to send a letter to yourself, instead of just dropping it on your > desk in the first place :^) According to the sieve documentation, sieve takes great pains not to lose mail, for example, with the implicit keep. Redirecting mail to your own address is a trap for the user, and it may be some time before she even realizes that mail is being lost. Sieve should not be allowing this to happen. > Even if duplicate suppression was turned off, there is no need for the > email to pass back through your MTA and lmtpd again. In fact, you'd get > into an endless loop. Yes, this situation should be avoided at all costs. -- -Gary Mills- -Unix Support- -U of M Academic Computing and Networking-
