AWL is loaded in v310.pre and can be disabled by commenting out the loadplugin line: # loadplugin Mail::SpamAssassin::Plugin::AWL To try TxRep out, you have to first disable the AWL plugin (if enabled), and back up its database. It adjusts the final message spam score by looking up and taking in consideration the reputation of the sender. The TxRep (Reputation) plugin is designed as an improved replacement of the AWL (Auto-Whitelist) plugin. Please see the site information for important legal information.Mail::SpamAssassin::Plugin::TxRep - Normalize scores with sender reputation records SYNOPSIS I use:Īny comments, suggestions, or improvements to the above are welcomed. The same principle is also true of the Razor scoring. This scoring is a lot more aggressive than the default, as I have had good experiences with Bayes. If you don't like this, like me, configure the BAYES scores manually. If you enable the Rela圜ountry plugin, you may want to add:īy default, the BAYES scores in SpamAssassin are generated using the genetic algorithm, and thus do not decrease and increase monotonically. Using spamassassin -D may help here to check the plugins are enabled. In my experience, it is particularly worthwhile making sure that the URIDNSBL plugin is enabled, as this can contribute highly to the score of a spam.
Read this file, read the manpages for the plugins, install any prerequisite Perl modules, and then uncomment them. This won't adversely affect your Bayes setup as long as the volume of these is sufficiently outweighed by 'real' spam.Ĭertain plugins in /etc/spamassassin/init.pre are often commented out by default. An example is blacklisting the occassional 'legitimate' organisation that sends you what you consider to be spam. And don't worry about the odd email being mis-learned (i.e.
Do use Bayes - it really does make a difference.Since ClamAV checks for phishing patterns and other similar attacks also, which tend to be time-critical, keeping its database up-to-date is important - you should probably use freshclam. I have had very good results using the ClamAV plugin to keep out virus-laden spam, although I would personally recommend using a lot lower value than the suggested score of 10, since no virus-check can be perfect. Purists will insist that spam and viruses are not the same thing, but they often arrive together, and you rarely want either.They make a large contribution to spam scores in general. If you have large volumes of email, a mailer such as mutt can be useful, where you can sort by spam score by adding something like: I still use a threshold of 8, despite the fact that incoming ham very rarely scores more than 5. Set your required_score parameter high until you are confident that you know what kind of score distributions your emails (both ham and spam) come in at - the last thing you want to happen is for any ham to be marked spam and overlooked.I've tried to avoid covering anything available in those other locations. They assume you have already installed SpamAssassin, are familiar with how it works, and know where to find the SpamAssassin documentation (in particular the SpamAssassin Wiki, which is a great jumping-off point for SpamAssassin FAQs, documentation, and other tips).
These tips are based on my observations of my use of SpamAssassin (currently at version 3.0.3) over several years.