On Thu, Apr 23, 2009 at 10:49:50AM -0400, Wietse Venema wrote:
> > We could call this feature frozen_owner_alias, and make the new
> > default "yes" (i.e. don't lose the owner-parent alias when delivering
> > to an alias without owner-child alias).
> >
> > This is similar in spirit to "frozen_delivered_to = yes" which
> > was introduced to stop undesirable behavior that resulted from
> > attempts to accurately attribute mail delivery actions.
>
> This breaks compatibility with some Sendmail versions. Specifically,
> when alias "foo" includes "foo" in its expansion, Postfix must
> deliver to the user "foo" instead of creating a mail loop (which
> is what frozen_delivered_to=yes would cause).
We could reserve the special treatment just for the current recipient
address (that would trigger loop detection) and deliver everything
else indirectly:
Safe to deliver to "user" indirectly, because "user" is not "foo":
aliases:
foo: :include:/some/path
bar: user
/some/path
bar
Must deliver to "user" directly, because "user" is the top-level
recipient:
aliases:
user: :include:/some/path
bar: user
/some/path
bar
Such loops are not that common in practice, and those who create them
can suffer the consequences of their folly. This means that indirect
delivery is never attempted for the original queue-file recipient that
got us into the whole mess.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majord...@postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
