From: (no name) (no email)
Date: Thu May 01 2008 - 17:02:26 EDT
> By default, :include:/file aliases already do indirect delivery, so
>
> > The owner-listname alias is required in any case, so that senders
> > don't get all the non-delivery notifications. Instead, they are
> > sent to a person who can actually fix the problem, for example by
> > removing dead addresses.
>
> the main benefit of "ower-listname" with ":include:..." aliases is
> redirecting the non-delivery notices. You only get multiple deliveries
> when:
>
> - The :include: alias member is listed with other "direct" recipients
> for the same alias, and some of those (soft) fail.
Viktor, it is friday morning and my brain isn't functioning as well as
it could (well that is my excuse anyway), so I am not quite sure I
understand you. Are you saying I could get multiple deliveries in a
case like so:
mylist-approval
mylist-outgoing-request
mylist-owner
mylist "|/usr/local/majordomo/wrapper resend -l mylist -h mail.com mylist-outgoing"
mylist-request "/usr/local/majordomo/wrapper request-answer mylist "
mylist-outgoing :include:/var/spool/majordomo/lists/mylist,
owner-mylist
owner-mylist-outgoing
and the soft fails? Is that what you mean by
other "direct" recipients? Or do you mean when someone sends an email
to mylist and (say) and the
soft fails? Or something else? sorry!
Thanks
Matt
|
|
|