If/when you use an alternate config file with the -C /pathto/majordomo.cf,
it must be the first argument used. Examples;
...wrapper resend -C mj-2.cf -l listname listname-outgoing,nobody
...wrapper majordomo -C mj-2.cf
...wrapper majordomo -C mj-2.cf -l listname
If the owner is a member of the list, they will receive messages. It could
also be possible, that the "nobody" user points to an address rather than
the typical /dev/null.
Dan Liston
Bealers wrote:
>
> Hi there
> I'm 99% finished setting up a MD list and have the list working and it's now
> being archived.
>
> I've just got a really annoying problem where any message posted to the list
> goes to the list AND the owner, how can I stop this please?
>
> thanks
>
> Darren Beale
>
> /etc/aliases =>
> #majordomo
> majordomo: "|/usr/local/majordomo/wrapper majordomo"
> owner-majordomo: admin
> majordomo-owner: admin
>
> #MajorDomo Aliases
> majordomo-1: "|/usr/local/majordomo/wrapper majordomo -C
> /usr/local/majordomo/majordomo-1.cf"
>
> #residents
> residents-request: "|/usr/local/majordomo/wrapper majordomo -l residents -C
> /usr/local/majordomo/majordomo-1.cf residents-OutGoing"
> residents-OutGoing: :include:/usr/local/majordomo/lists/residents,
> residents-archive
> residents: "|/usr/local/majordomo/wrapper resend -l residents -C
> /usr/local/majordomo/majordomo-1.cf residents-OutGoing,nobody"
> residents-archive: "|/usr/local/majordomo/wrapper archive2.pl -f
> /usr/local/majordomo/lists/residents.archive/residents -m -a"
Follow-Ups:
References:
|
|
