I use a couple tricks to prevent loops, but specifically to
prevent auto-reply loops, I do this in the majordomo.cf file;
$global_taboo_body = <<'END';
/I (am|will be) .*(office|vacation)/i
$majordomo_dont_reply = '(mailer-daemon|uucp|listserv|majordomo|listproc|auto-reply)\@';
The first regex in the taboo_body setting will prevent my
approval password from being accidentally distributed to
the list. The second one may catch announcements that are
not really auto-replies, but better to catch the few of
these than to let any mail loop start.
I also found that compuserve tends to send their user's
vacation messages "From: auto-reply", so I instruct
majordomo not to reply to this robot.
Robert Miller wrote:
> Hmm... do you think my boss will be upset with the 20,000 messages sent in responce to her on-vacation notice?
> In an emergency, I had to comment the following line to break the loop:
> # majordomo: "|/var/majordomo-1.94.5/wrapper majordomo"
> All lists have 'reply_to' set as $SENDER. However, the 'reply_to' option has no effect on the majordomo account.
> The documentation is unclear on the cause of this loop and how to break loops without disabling one/many mail accounts. How can I stop loops without hacking the /etc/aliases/ file? How can I prevent future loops?
> Thanks for a speedy reply,
From: "Robert Miller" <RMILLER@mail.gov.nf.ca>