> well, it had forged headers similar to spam....
Yes. It was spam. My apologies.
The annoying thing is it was sent to [EMAIL PROTECTED]
rather than [EMAIL PROTECTED] [EMAIL PROTECTED] is supposed
to be a secret address that nobody knows about that is the final
address majordomo forwards a message to after it has been accepted
at [EMAIL PROTECTED] and has made it past the anti-spam features
in majordomo designed to block things like this.
Unfortunately it looks like sendmail is leaking information in
the headers it sends out that makes it possible for people to
discover the supposedly secret [EMAIL PROTECTED] address.
I've changed things so that the spammers won't be able to use
this address for spamming the list any longer. Unfortunately
I don't know how to stop the new outgoing address name from
leaking out in the headers so that a smart spammer who finds
an archived copy of a list message on the web might once again
be able to figure out how to spam the list.
I am open to suggestions.
I use sendmail and majordomo, and my sendmail aliases file looks
something like:
mersenne: "|/home/gordoni/local/linux/majordomo/wrapper resend -l mersenne
mersenne-outgoing-queue99"
mersenne-digest: mersenne
mersenne-outgoing-queue99:
:include:/home/gordoni/local/linux/majordomo-data/lists/mersenne,
"|/home/gordoni/local/linux/majordomo/wrapper digest -r -C -l mersenne-digest
mersenne-digest-outgoing-queue99"
mersenne-digest-outgoing-queue99:
:include:/home/gordoni/local/linux/majordomo-data/lists/mersenne-digest
Although the queues aren't actually called "-outgoing-queue99".
thanks,
gordoni (list admin)
_________________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.exu.ilstu.edu/mersenne/faq-mers.txt
