For this to have happened, your subscriber must have been one of the few
allowed to post to the list in the first place. Nobody should ever post
as the majordomo ID, except majordomo when replying to list commands. If
someone is posting as majordomo, that last line of majordomo.cf should
prevent a mail loop from happening.
Another way to prevent a mail loop from happening, is to set the reply-to
address different than the sender's address, but you would never want to
to this with the actual majordomo address.
If you know what the auto-reply looks like, you can add text to the taboo
filters in majordomo.cf to catch these messages and deliver them to the
majordomo-owner alias, instead of letting the messages loop between
automated machines.
The best way to send a newsletter is from the newsletter-owner address,
not the majordomo address. With the restrict_post setting, you can
control on a per list basis, who can write/send the newsletter without
having to give them permissions to majordomo itself.
Dan Liston
Tobias Gablunsky wrote:
>
> hi all.
>
> I recently had a problem with a subscriber of one of my lists. my majordomo
> and his auto-reply were having a nice smalltalk. I give you the alias to
> which the auto-reply went:
>
> majordomo: "|/usr/lib/majordomo/wrapper majordomo"
>
> Do I have to use an additional resend with it or is it generally not the
> best way to send a newsletter (only a small amount of people are allowed to
> post) in the name of Majordomo himself ("sender" and "reply to")?
>
> thank you!
>
> tobias gablunsky
References:
|
|
