My apologies for the duplicate messages.
The first three were sent before I realized the messages were being
caught by administrivia checks.
When I realized these three had been caught, I assumed the list-owner
would not approve them after seeing the fourth message had already
been distributed.
Loop disasters:
I have received a couple of notes about similar loop disasters... the
resend.README says that it is "hoped" that "reply-to" could be made
intelligent enough to stop loops by 1.92.
I assume this isn't the case? Therefore, it is either necessary to
disable the "reply-to" feature (since a loop is inevitable, eventually),
or write custom code to check for it. (Please confirm this impression).
If someone else has written a loop prevention routine, I'd appreciate
a copy of the code (if possible).
Sincerely,
Thomas Leavitt
--
Web Communications (sm) Thomas Leavitt--leavitt@webcom.com
Voice: (408) 457-9671 x101 Lead Systems & Network Admin./Tech Suppt.
<a href="http://www.webcom.com/";>Web Communications Home Page</a>
Follow-Ups:
|
|
