John Hascall:
> *alias: :include:/list/of/members/in/a/file*
>
> So in the included file is it just one recipient per line or ?
One per line. This the same format that is maintained by some mailing
list managers.
Do not forget to set the "owner-alias: realuser@realdomain", so
that delivery errors are reported centrally.
Wietse
> Thanks again,
> John
>
>
> On Fri, Nov 7, 2014 at 12:48 PM, Viktor Dukhovni <[email protected]
> > wrote:
>
> > On Fri, Nov 07, 2014 at 12:05:03PM -0600, John Hascall wrote:
> >
> > > THANK YOU!
> >
> > Note, however, that expansion of long local aliases can be very
> > fragile. If you list "$myorigin" in "mydestination", the delivery
> > to all the users needs to succeed, or all are retried again if even
> > one delivery fails (mailbox over quota, ...).
> >
> > It is far better with long aliases to use indirect delivery:
> >
> > alias: :include:/list/of/members/in/a/file
> >
> > This form is always delivered indirectly, with a new queue file
> > for the expanded list of recipients.
> >
> > If your user accounts are not "local" ($myorigin is not listed
> > in $mydestination) and aliases are only uses for lists:
> >
> > mylist: user1, ..., userN, continue-1@localhost
> > continue-1: ..., continue-2@localhost
> > continue-2: ...
> >
> > then delivery to the users is automatically indirect, but the
> > continuations are processed recursively, and there is no problem.
> >
> > However, with large lists you also REALLY SHOULD have an "owner"
> > alias:
> >
> > owner-mylist: someone
> >
> > Finally, I recommend handling list expansion via virtual(5) not
> > aliases(5). As much as possible, use aliases(5) only for pipes to
> > commands and ":include:".
> >
> > --
> > Viktor.
> >
