As the cornerstone of spam-mitigation efforts, enabling SpamAssassin is an essential step to ensuring your users have a positive mail experience. As with most things server administration, there is far more to consider than merely enabling it. Often, the system administrator must optimize the service to achieve peak performance for their users.
Below you'll find articles to help you on your journey to providing a spam-free mailbox to your users.
Articles for consideration
The first step to increasing SpamAssassin's effectiveness is identifying how and why a given spam message was or was not correctly flagged. These links provide some important troubleshooting steps for determining what is necessary:
Why are messages moved to the spam folder?
How can I check why Spam Assassin applied a particular score?
Spam messages getting through without being scanned? This article shows why that may be the case:
Why is SpamAssassin not scanning certain emails?
It is not uncommon for SpamAssassin to scan a message, but not flag it as spam because it did not trigger the right rules, or enough of them to accumulate a score exceeding the configured threshold. These articles illustrate several methods to address that:
How to Make a Custom Configuration File for SpamAssassin?
How to teach Spam Assassin to identify more SPAM
How to adjust the weight of a SpamAssassin rule?
Is it possible to create custom rules for SpamAssassin?
Where can I find additional rule sets for SpamAssassin?
Can I submit my spam to SpamAssassin to help block messages like it in the future?