On 08/22/2014 08:23 PM, Carlos E. R. wrote:
On Thursday, 2014-08-21 at 12:00 -0400, Anton Aylward wrote:
One reason I have spamassassin in procmail rather than up front in Postfix is that I have many procmail rules BEFORE I apply spamassassin.
* if the ISP has already labelled it is SPAM then put it in the SpamBox right away
I don't. Often, the ISP does the wrong checking,
Mine does too. That's whay I have varying levels of spambox and why I have whitelisting of known things, regardless of what the ISP says, up frot. The idea is to reduce the load on spamassassin. Actuall I have 10Spam 20Spam 30Spam 40Spam 50Spam blacklist fontSpam isSpam probablySpam noSubject numericIP and only after checking fo items get deleted or put in spam-learn or spam-unlearn But the point is that where possible and where sensible I deal with it before spamassassin because of the comparative cost & delay of spamassassin processing.
* if its for any one of a number of lists that I subscribe to, the put it in the list folder right away.
Again, I don't: I see spam email on several of the mail lists. On some I get a lot (the xfs mail list, for instance). So I let SA check.
What's this with being absolutist? There are lists I'm on that are, unlike this one, closed/subscription only. You can't just automatically sign up. Even on this one, spamming is very very rate and I can put up with that, deal with it manually. I don't want SA to ;earn "[opensuse]"
Having bracketed list markers on the subject line is nice :-)
I don't look at them at all. I look at the "X-Mailinglist" header instead.
Being absolutist again? Actually I have a 'trust but verify' with nested tests. If the subject like has "\[.*\]" then and only then do I bring in the mailing list processing rules and look at the other fields. Did I mention I have a highly modular procmail? ~anton/.procmail/<modules> Procmail is very good with patterns!
* if its not in English, put it in the ForeignBox right away
I'm bilingual, so I have to handle emails it two languages every day. I don't sort by language.
About 99.8% of what gets rejected by that module is non-european characters. Mostly Asian. I can make some sense of most of the "Romance" languages having studied Latin and Greek at school, but the Asian ones I can't make sense of. Don't you get any in Asian and Russian character sets?
* if it meets a pile of garbage conditions them put it in the SpamBox
* if its from a 'whitelist' of senders don't bother with spamassassin (yes I know spamassassin has a whitelist; this is faster)
But not as precise; and it is easier to maintain SA than a huge lot of procmail recipes (and I have a lot).
YMMV. I find procmail easier to maintain than SA. SA needs to be compiled; procmail I just add to a test file: This is the "long" version of the whilelist.rc module that makes it all very obvious. --------------------------------------------------- # Test if the email's sender is whitelisted; if so, send it straight to # $DEFAULT. Note that this comes before any other filters. :0: * ? formail -rt -x"From" -x"From:" -x"Sender:" \ -x"Reply-To:" -x"Return-Path:" -x"To:" \ | egrep -is -f ${HOME}/.whitelist { LOG="Found on whitelist$NL" $DEFAULT } So all I have to do is edit ~/.whitelist ------------------------------------------------------ If there's a way to use an external dynamically modified list with SA, one that includes patters as well, I haven't found it.
All this relieves SpamAssassin of a lot of processing. However you cut it, SpamAssassin is a choke-point. Only using it when I have to relieves a big load.
I find it easier to let it run and do its job, that have me thinking and adjusting rules and filters all the time.
Well EXCUSE ME! This isn't an "all the time" any more than running sa-learn is "all the time". It was all up-front thought and design, put in place, tested AND THEN LET RUN. Apart from adding to whitelist or blacklist, which I haven't had to do in the last 4 months, this is maintenance free. back in the resource starved 800MHz 1G RAM system that was out of the Closet of Anxieties and was the mail hub, this was great. I've had not reason that change it. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org