Someone definitely throwing a nasty mailbomb into
the Arachne list! Could this be related to the
recent LANR incident?
Tonight I received at least four fat Arachne digests.
All of them verified from the majordomo. So, the
digest version should be OK. However, all of these
digests contains lots of duplicates. This clearly
indicating a severe mail loop.
Bad news is:
* A majordomo has no loop protector. Anyone
could easily mailbomb a majordomo list by
subscribe with an e-mail forwarder then
change it's forwarding address back to the
list address, effectively creating a loop.
Good news are:
* There's a limit for the number of hops a mail
can be forwarded. Excess this and the mail
will be bounced back. So, you'll get a limited
count of duplicates or so and no more.
* Members of the main Arachne list could easily
track the forwarder address by comparing the
"Received" header lines in the duplicated
postings.
The ultimate question is:
Could we track that bad guy/gals/whatever who
mailbomb Arachne list? There's should be some
log stored at the forwarding ISP about what the
previous destination address was. But then,
will they help?
--Eko
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
