On Wed, Nov 14, 2001 at 10:21:15PM -0800, Professional Software Engineering
wrote:
Nothing specifically for that. But as I previously stated, the _SAME_
rules you'd apply to regular mail would apply there. Try any one of the
several anti-spam procmail kits there exist already.
Actually, I'm using a collection recipes that I've posted at
http://www.it.ca/software/procmail-spamtrap if you want to take a look.
I find that my spamtrap is lighter weight than Catherine Hampton's
spambouncer, but still gets 95% of the same junk.
Ah, well this works ok for the majordomo administrative address -- the
individual lists have several parameters which need to be passed, and thus,
All my current lists restrict posts to members only, so I'm not too
worried about that. I'll probably implement your suggestion anyway, for
the ability to screen list submissions for size and other content.
Actually, it's not even that. I'm trying to block messages to MAJORDOMO,
not messages to the lists.
Your original message did not make this clear - "majordomo" is a list
processor, and without specifying that you're processing only the primary
administrative address, it would be taken to assume the whole lot of
majordomo lists on a server.
Hmm, I guess I figured my original query would be taken at face value
rather than interpreted. I said "sent to majordomo", and talked about
"majordomo responses", which I wouldn't think includes list expansion.
Sorry about the lack of clarity.
Suggestion: change the majordomo alias, like so:
majordomo: "|/usr/local/majordomo/wrapper majordomo",testuser
Excellent suggestion. Thanks. I keep forgetting about sandboxes.
# transferred from aliases.majordomo...
:0
* ^TO_majordom(_at_)it(_dot_)ca
! majordomo-owner
I presume you're saying "send me a copy of everything anyway, even if it's
spam" ?
No, I'm duplicating the functionality of the original aliases file, which
forwarded mail to the user "majordom" to the majordomo-owner alias (as
opposed to processing the alias "majordomo" with the wrapper).
* ! ^To:(_dot_)*majordomo(_at_)${MYDOMAINS}
Because there's inherently no legit reason someone should be CC'ing or
BCC'ing commands to majordomo. People deliberatley mail it to send a
command. Granted, cc and bcc work currently, since majordomo doesn't care
how it was addressed so long as it was invoked, but the point is, ask
yourself why anyone would cc or bcc majordomo (perhaps they'd be sending a
Good point. Assuming I've created support for this in the aliases file,
should the following cover all the common variations?
* ! ^(To|CC):.*(majordomo|.*-((un)?subscribe|request))@${MYDOMAINS}
Uhm, what about the possibility that these keywords might appear in the
SUBJECT?
According to the majordomo help message, "Majordomo does not process
commands in the subject line." Perhaps other list managers operate
differently.
Anybody see any problems with it? Is it safe to assume that any
legitimate email for majordomo will contain at least one majordomo
command in the body?
That's a judgement call - if someone sends a blank message (which may still
include their .sig, so empty body isn't a valid definition for "blank"),
they might expect to recieve a help response (which majordomo won't give
them - but then it'd at least RESPOND). As written, these people will get
shuttled into the spamtrap...
Hrm. I'll leave out the body content filter and see how it goes over
the next week or two. Perhaps the other rules will be sufficient to
cut down on the bulk of the garbage.
Thanks for your advice.
--
Paul Chvostek
<paul(_at_)it(_dot_)ca>
Operations / Development / Abuse / Whatever vox: +1 416 598-0000
IT Canada http://www.it.ca/
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail