>On Thu, 7 Jul 2005 13:31:45 -0400 (EDT), you wrote:
>Recently, I've been seeing a fair number of spam messages that
>have been sent to my majordomo address. They are sent from bogus
>"From:" addresses, and since majordomo doesn't need Viagra, etc,
>"he" replies with a long stream of error messages:
>&squawk("Command '$cmd' not recognized.");
>This message with every line parroted back as "not recognized" PLUS
>the majordomo help text is then sent to the fake "From:" address,
>and the isp, if it exists, sends it BACK to me complaining about
>a non-existant user. As majordomo-owner, I get it in my inbox.
>To put a stop to this, I modified majordomo in the following ways:
>I added a threshold of 10 "not recognized" errors, which if exceeded
>AND we have NOT SEEN ANY valid commands, the following actions take place:
>1. Processing of the message is terminated.
>2. The help text is not sent.
>3. Instead of replying to the "sender", we send just send a short
>note to majordomo-owner that says a message with > THRESHOLD errors was
>found and a reply was NOT sent to "sender".
>I'll be happy to make this code available in any way that is appropriate.
I'm having a similar problem here with spam going directly to the list
addresses such as the digestify etc. Do you know a way I can stop this
from getting in my digests as I am now to the point where it will
generate a digest of only spam...I'm running spamassassin here and
looking for various taboo headers and X-Spam type stuff but somehow
they seem to get the messages past the spamassassin step.
Feel free to reply off list if you feel its not appropriate here on
I can provide samples or my settings if needed
===[George R. Kasica]=== +1 262 677 0766
President +1 206 374 6482 FAX
Netwrx Consulting Inc. Jackson, WI USA