We also had a problem with our moderated list and the system analyst
discovered yesterday that our aliases for moderated were "stepping on
themselves" - following is an EXAMPLE of the re-generated aliases that
ended up working for us. Hope this is of some help. I always like
examples of the real thing myself.
#dummy
owner-dummy: real-name@real.address
dummy: "|/usr/users/majordom/wrapper resend -l -h realcomp@real.address
dummy-outgoing"
dummy-outgoing: :include:/usr/users/majordom/list/dummy
owner-dummy-outgoing: owner-dummy
dummy-owner: owner-dummer
dummy-request: "|/usr/users/majordom/wrapper request-answer dummy"
owner-dummy-request: dummy-owner
dummy-approval: realname@real.address
On Thu, 16 Oct 1997, Siamak Farah wrote:
>
> Ok, I am thoroughly baffled. Below is the list of my aliases for a list I
> have (called wed@alborzi.com)
>
> I would think that any bounces, whether it is a bad email, or an
> unauthorized person, or message size to large should come to the owner, not
> the entire list. But mine goes to the entire list. Can anyone tell me why?
>
> #{----- Aliases for the wed list -----
> #
> wed-owner: webmaster@alborzi.com
> owner-wed: webmaster@alborzi.com
> owner-wed-outgoing: wed-owner
> owner-wed-request: wed-owner
> wed-approval: wed-owner
> wed: "|/www/majordomo/wrapper resend -p bulk -M 10000 -R -l wed -f wed -h
> alborz
> i.com wed-outgoing"
> wed-outgoing:
> :include: /www/majordomo/lists/wed
> wed-request: "|/www/majordomo/wrapper request-answer wed"
> #
> #------ End of Aliases for the wed list -----}
>
>
>
References:
|
|
