On 11 Feb 99, at 12:43, Rich Greenberg wrote:

>
> Nathan, could this get us into trouble in some condition I am not aware
> of?

Here's a little test you can do. Set Loopcheck=None in your list header.
Then add [log in to unmask] (I'm assuming this is a non-
existent address) to the list. Then send a message to the list. Then sit
back and watch as the mail keeps piling in as compuserve sends its
bounce to the wrong address, namely the list address, the bounce gets
distributed to the list because it didn't get trapped by LISTSERV's
loopchecking which under normal circumstances would have caught the
header that compuserve kindly appends to the bounce message. Then
the bounce bounces, and that bounce gets delivered, only to bounce
back to the list again, and so on and so on forever and ever.

PLEASE DON'T REALLY TRY THIS!!!! Your mail admins will hate you,
your subscribers will hate you, your subscribers' mail admins will hate
you, other list owners will hate you for bringing the server to its knees,
your LISTSERV admin (who also will hate you) will have to bring down
the LISTSERV server to trap the bounces, and it will cause all sorts of
headaches for all involved. Trust me on this: it's not fun to deal with
when two programs with conflicting orders start sending mail to each
other.

Fortunately, LISTSERV catches the Sender: pointing to the list in the
forwarded part of the bounce, and so all that really happens on a normal
list is that the list owner gets that annoying error message about
Sender: pointing to the list found within the body of the message.

Francoise