Eko wrote:
>Someone definitely throwing a nasty mailbomb into
>the Arachne list! Could this be related to the
>recent LANR incident?
Actually it appeared a few hours before. (I noticed that mails I sent
hadn't arrived after quite some time then the next day Michaels mail was
sent out (and the date/time on those where as far as I could tell after I
had sent mine)).
>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.
Yes, but as I have pointed out on the Arachne list not everyone seems to
have this problem. And it's affecting all of the lists - but ex.
arachne-devlopment the only duplicates there are those Michael has sent
himself. None of the others (what I can tell anyway). In the main list some
peoples mail doesn't get duplicated (besides it was noticably less for a
day or two).
>* 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.
And the sollution is? The same thing could happen here could it not?
>* 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.
Between 1 and 3 duplicates AFAIK (but pressing "Del" all the time is boring!)
>* Members of the main Arachne list could easily
> track the forwarder address by comparing the
> "Received" header lines in the duplicated
> postings.
Some brazilian address seems to be the one - according to others. I can't
figure out how to get Eudora to show me more of the headers.
>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?
Probably, since most ISP takes spamming quite seriously and IMO this is a
spamming problem.
Untill everything is fixed I'm quiet on that list.
//Bernie
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.
