Gary Mills wrote:
>
> On Thu, Dec 13, 2001 at 09:03:45PM -0500, Ken Murchison wrote:
> >
> > Gary Mills wrote:
> > >
> > > On Thu, Dec 13, 2001 at 11:21:14AM -0500, Ken Murchison wrote:
> > > >
> > > > 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.
> >
> > Hmm... Well, this won't as-is for the same reason that people need to
> > specify :addresses for vacation. The envelope recipient when retrieved
> > by sieve is unqualified (ie, no domain) and the redirect address is (as
> > is required by the Sieve parser).
>
> I posted a patch recently that re-qualifies the envelope recipient
> with the same domain as used by the MTA. It also fixes an apparent
> bug in the handling of route addresses. The domain used to qualify
> the envelope recipient is taken from the `servername' configuration
> parameter, which defaults to the hostname of the server. The patch
> is for imap/lmtpengine.c. I'll attach a copy.
It look like your patch blindly attaches the entire servername, which
may not be correct for some installations. Larry, Tim Showalter and
myself have had several discussions about how Sieve should determine a
user's email address, and haven't come up with any good answers. So, as
you can tell, we've punted.
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
