{"id":213,"date":"2004-08-31T08:50:23","date_gmt":"2004-08-31T07:50:23","guid":{"rendered":"http:\/\/wp.devco.net\/?p=213"},"modified":"2009-10-09T17:18:04","modified_gmt":"2009-10-09T16:18:04","slug":"fine-tunning_spamassassin","status":"publish","type":"post","link":"https:\/\/www.devco.net\/archives\/2004\/08\/31\/fine-tunning_spamassassin.php","title":{"rendered":"Fine-tunning SpamAssassin"},"content":{"rendered":"
Via RootPrompt<\/a> I found a nice article titled Fine-Tuning SpamAssassin<\/a>. It covers quite a bit of detail about SpamAssassin and is well worth a read.<\/p>\n \nOver time, however, many of the spammers have figured out how to fine tune their spam and bypass the default ruleset. I find the default setup still picks up at least half the spam, maybe two thirds on a good day, but too much leaks through. If the spammers are tuning their messages, I guess the only thing to do is to tune my scoring. There are at least 8 possible ways of improving SpamAssassin’s hit rate. Via RootPrompt I found a nice article titled Fine-Tuning SpamAssassin. It covers quite a bit of detail about SpamAssassin and is well worth a read. Over time, however, many of the spammers have figured out how to fine tune their spam and bypass the default ruleset. I find the default setup still picks up at […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","footnotes":""},"categories":[5],"tags":[30,19,29,33],"_links":{"self":[{"href":"https:\/\/www.devco.net\/wp-json\/wp\/v2\/posts\/213"}],"collection":[{"href":"https:\/\/www.devco.net\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devco.net\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devco.net\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devco.net\/wp-json\/wp\/v2\/comments?post=213"}],"version-history":[{"count":1,"href":"https:\/\/www.devco.net\/wp-json\/wp\/v2\/posts\/213\/revisions"}],"predecessor-version":[{"id":774,"href":"https:\/\/www.devco.net\/wp-json\/wp\/v2\/posts\/213\/revisions\/774"}],"wp:attachment":[{"href":"https:\/\/www.devco.net\/wp-json\/wp\/v2\/media?parent=213"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devco.net\/wp-json\/wp\/v2\/categories?post=213"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devco.net\/wp-json\/wp\/v2\/tags?post=213"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n1. Blacklisting known offenders
\n2. DNS Blocklists
\n3. Enable Bayesian filtering
\n4. Reduce the point threshold for spam
\n5. Increase the scores on existing rulesets
\n6. Upgrade SpamAssassin to the latest version
\n7. Install more rulesets
\n8. Write your own rulesets\n<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"