When I set mine up I do 2 things that I think are important to avoid these
1. Initialize the vacation.db and NOT set it to "0" (zero) which means that
vacation will only reply once to that email address - if you set it for 7
it will reply once and stay in effect for 7 days. eg: To initialize the
~billh> vacation -i -r 7
-i Initialize the vacation database files. It should be used before
you modify your .forward file.
-r Set the reply interval to interval days. The default is one
week. An interval of ``0'' means that a reply is sent to each
message, and an interval of ``infinite'' (actually, any non-nu-
meric character) will never send more than one reply. It should
be noted that intervals of ``0'' are quite dangerous, as it al-
lows mailers to get into ``I am on vacation'' loops.
2. In the vacation.msg file I make sure that I set the header to include
"Precedence :Bulk" eg: Part of my .vacation.msg file
Subject: Email reply Notice
Delivered-By-The-Graces-Of: Email Notify
This is an automated response and will only be sent once to alert you..
blah blah blah...
This from my understanding will keep a listserver from accepting the email
in the first place if it rejects "bulk" mail.
Hope this helps,
At 12:20 PM 7/10/98 -0600, you wrote:
>I've read the FAQ and three months of archives, and Jason
>Tibbit's searchable index server is not responding, so here goes...
>How do you stop an automatic reply program (like vacation on Unix)
>from causing an infinite mailing loop? That is, a message goes out,
>the auto-replier sends back to the list, which sends back to the
>which sends back to the list, ....