![]() Loadplugin Mail::SpamAssassin::Plugin::TextCat Only accept email in specified languages - TextCat This rule set is no longer maintained and due to its design may have randomly harmful effects on scoring. SoughtRules was a custom rule set generated from spam 4 times a day by a SpamAssassin developer. They are not included in SpamAssassin by default, but often have been added to local configurations. SARE rules have not been updated in years, and are therefore actively harmful. If they are causing counterproductive scores, the only solutions are to delete the relevant databases and start over training them, or disable them with: Verify they are providing useful scores - positive scores for spam, and negative scores for ham (AWL and BAYES_* tests). The AutoWhitelist, and Bayesian classifier when automatically trained, can get trained incorrectly, resulting in scoring email wrong. Verify AWL and the Bayesian classifier aren't poisoned ![]() But if you're receiving a significant portion of your email via a trusted relay, it needs to be listed in one of these manually, otherwise the wrong hop will be used for things like DNS blacklist tests. Often, spamassassin will intelligently do the correct thing by default. If they're installed correctly, the debug output of SpamAssassin will include:Īpr 14 16:24:37.315 dbg: plugin: loading Mail::SpamAssassin::Plugin::Pyzor from 14 16:24:37.318 dbg: pyzor: network tests on, attempting PyzorĪpr 14 16:24:37.318 dbg: plugin: loading Mail::SpamAssassin::Plugin::Razor2 from 14 16:24:37.381 dbg: razor2: razor2 is available, version 2.84Įnsure that internal_networks and trusted_networks are set correctly. These are two helper applications with useful (network) rules. You should run a local caching DNS server for efficiency.Īs of, without network tests, SpamAssassin is wrong 2.58 times as often on non-spam, and 3.40 times as often on spam. DNS rules may have been disabled with " dns_available no" in local.cf. Network tests may have been disabled by running spamassassin or spamd with the command line arguments -L or -local. This is the default, but disabling network rules (including DNS rules) causes SpamAssassin to be wrong on about 3 times more emails. (On Debian based systems, set "CRON=1" in /etc/default/spamassassin - this is not the default.) Enable network rules ![]() This is often included in SpamAssassin packaging, but sa-update should be run from cron daily, to get the latest SpamAssassin rules which are generated every day. Regular updates of SpamAssassin 3.2.x rules stopped in 2008. How to Improve SpamAssassin Accuracy Run a recent version
0 Comments
Leave a Reply. |