Re: How to filter on Spamassassin headers with Majordomo2 ...
Brock Rozen <[email protected]> Tue, 9 Sep 2003 23:23:22 +0300 (IDT)
| Newsgroups | gmane.mail.majordomo.majordomo2.devel,gmane.mail.majordomo.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, How do you deal with any other types of action that are NOT posts? Our only option was to go with block_headers, which generates a lot of traffic to the owners, but manages to block out lots of traffic that simply blocking "post"-only doesn't do. Besides that, it's already doing it's work wonderfully. Best, BR On Tue, 9 Sep 2003 at 17:09, Marc G. Fournier wrote about "How to filter on...": > > Since I've seen a couple of questions on this over the past few days, here > is what I have in place to filter based on SA headers for the > PostgreSQL.Org mailing lists: > > configset DEFAULT taboo_headers <<ENDAAB > /^X-Spam-Status: Yes/ 10,spamassassin > /^X-Spam-Status: Yes, hits=([6-9]|\d\d+)/ 20,spamassassin > /^Subject: Thank you!/ 1,virus_subject > /^Subject: Re: Thank you!/ 1,virus_subject > /^Subject: Re: Wicked screensaver/ 1,virus_subject > /^Subject: Wicked screensaver/ 1,virus_subject > /^Subject: Re: Re: My details/ 1,virus_subject > /^Subject: Re: That movie/ 1,virus_subject > /^Subject: That movie/ 1,virus_subject > /^Subject: Re: Approved/ 1,virus_subject > /^Subject: Approved/ 1,virus_subject > /^Subject: Re: Details/ 1,virus_subject > /^Subject: Re: Your application/ 1,virus_subject > /^Subject: Your application/ 1,virus_subject > /^Subject: Re: Your details/ 1,virus_subject > /^Subject: Your details/ 1,virus_subject > /^Subject: Details/ 1,virus_subject > ENDAAB > > configset DEFAULT access_rules <<ENDAAB > post > deny, reason="The message is too big" > $body_length_exceeded > > post > deny, reply=NONE > $taboo_spamassassin > 6 > > post > consult, reply=NONE > $taboo_spamassassin > > post > deny, reply=NONE > $taboo_virus_subject > ENDAAB > > > Hopefully this helps some out there ... > -- Brock Rozen [email protected]