I've got a user who is misusing spamassassin as follows:
Only use it for its whitelist capability. (But wait, there's more...)
Why is this bad? Several reasons. First, we were feeding it thru procmail
with a filter to only run SA if the msgs is >256K so some inbound messages
(eg with attachments) wont even hit this. Second, after running (or trying
to run) SA, check for the SA headers. If spam, put in spam, if SA header is
present but it's not spam, put in an isolation chamber (let's call that
"rejected") Now run a whole bunch of procmail tests: if from this user or
that user, drop in junk...
Further, the whitelist while explicit for some addresses, is WIDE open for
others (eg *.gov). Yet magically, this crazy filtering scheme has worked up
until now (and could presumably work forever if the msg size test were
pulled off.)
So for people who generally only converse with a known, albeit lengthy and
perhaps not completely defined list addresses the question is, is there
a better way of filtering. I'm thinking just pull SA out of this equation
have a file with regexp addresses that procmail tests all in a single test
and be done with it.
TIA
=-=-=-=-=-=-=-=-=-=-=-=- generated by /dev/dave -=-=-=-=-=-=-=-=-=-=-=-=-=-=
David Stern University of Maryland
Institute for Advanced Computer Studies
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail