So my mailing lists are getting hit by spam that goes to the lists since it claims to be from some poor subscriber whose email got hijacked. But to be more general, what are some of the current best practices to filter out spam in a postfix mailman environment on Linux?
mjb.
Mark J Bradakis writes:
So my mailing lists are getting hit by spam that goes to the lists since it claims to be from some poor subscriber whose email got hijacked. But to be more general, what are some of the current best practices to filter out spam in a postfix mailman environment on Linux?
Run SpamAssassin or similar as a milter from Postfix.
One hint that may help is that on many lists there's a short list of keywords that allow you to whitelist content when they appear in a text/* part. Eg, on Python lists, almost no spam contains the word "python" (except perhaps in the greeting "Dear python-list@python.com"). SpamAssassin and similar filters allow you to add rules for this kind of thing.
Am Dienstag, 15. Mai 2012, 03:54:21 schrieb Mark J Bradakis:
So my mailing lists are getting hit by spam that goes to the lists since it claims to be from some poor subscriber whose email got hijacked. But to be more general, what are some of the current best practices to filter out spam in a postfix mailman environment on Linux?
Since we are using greylisting in addition to clamav (+ clamav-unofficial- sigs) the amount of spam decreased once more. I don't remember when the last customer complained about having unsolicited e-mails.
Regards, Rainer
Mark J Bradakis wrote:
But to be more general, what are some of the current best practices to filter out spam in a postfix mailman environment on Linux?
I use greylisting with Postgrey and spam/virus/other scanning via MailScanner.
Also to increase protection against hijacked list member's accounts, on my largest, highest traffic list I have set Privacy options... -> Recipient filters -> max_num_recipients to 5 although this does result in some held posts due to the recipient list growing after multiple reply-alls.
I also hold messages with no or empty Subject: header. I happen to do this with a custom handler that also holds messages that quote digest boilerplate, but it can be done with header_filter_rules.
Other things I hold with header_filter_rules are these:
^Sender:.*linkedin.com>?$ ^Return-Path:.*linkedin.com>?$ ^Sender:.*homerunmail.com>?$ ^Return-Path:.*homerunmail.com>?$ ^Reply-To:.*homerunmail.com>?$ ^Sender:.*facebookmail.com>?$ ^Return-Path:.*facebookmail.com>?$
I also have
^.*[@.]apot(mail)?\.com$
in all my lists' ban_list. This is not anti-spam, but is to prevent answerpot from subscribing to lists for the purpose of archiving them.
If MailScanner seems too heavy a hammer for spam/malware filtering, alternatives are http://sourceforge.net/apps/trac/fuglu/ or simply running spamassassin and clamav via milters.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
<< On 5/14/2012 8:54 PM, Mark J Bradakis wrote:
So my mailing lists are getting hit by spam that goes to the lists since it claims to be from some poor subscriber whose email got hijacked. >> Mark, it's nowhere near as bad as the same type/subject Yahoo Lists ! ! ! But to be more general, what are some of the current best practices to filter out spam in a postfix mailman environment on Linux? About 3 years or so, Bluehost started offering Spam Assassin and it has really done the job on my Lists. I actually cannot recall the last time I have seen a SPAM get through to a List.
Ed Please visit MY site at: www.justbrits.com
PS: Anyone interested in a slow ( 3- 4 /day) "Joke List" by MM, please drop me a note ! ! Ooops, and/or a small Political List (Poly Sci101).
participants (5)
-
" Just Brits " Shop
-
mailman@uni-duisburg-essen.de
-
Mark J Bradakis
-
Mark Sapiro
-
Stephen J. Turnbull