Wietse Venema:
> > Sorry, don't do that. Postfix will NOT store mailing list members
> > in the "new" queue file if that member is an alias.
> >
> > I haven't had time to fix local delivery agent logic since 1998,
> > and it is unlikely to be fixed now without unexpectedly breaking
> > a ton of other things, such as:
> >
> > - Instead of failing with a mail delivery loop, deliver mail to
> > the user FOO when FOO is an alias that contains FOO (or an alias
> > for FOO).
> >
> > - Instead of failing with a mail delivery loop, deliver mail to
> > the mailbox FOO when ~FOO/.forward contains FOO (or an alias for
> > FOO).
> >
> > And other Sendmail compatibility.
>
> At this point the best I could do is make the alias expansion
> behavior configurable with a backwards-compatible default setting.
>
> Specifically, this would involve a switch that turns off alias
> expansion once Postfix starts delivery to an alias FOO that has an
> owner-FOO alias. This would solve the problem for mailing lists,
> but could create mail delivery loops that currently don't exist.
>
> Once this switch is fielded we can see if it introduces any surprises.
This would break recipient duplicate elimination when delivering
mail to a nested list (i.e. one mailing list has a member that is
the name of another mailing list), so this is not a useful solution.
Another possibility is to change alias processing so that it sends
recipient addresses to the "new" queue file (i.e. everything except
delivery to command or file).
Wietse
