Spamassassin was the first spam filtering system I tried, and because it worked so well, I've ended up using it for several years.
It isn't perfect though, it does require a lot of resources to operate, and it isn't incredibly fast.
Spamassassin Configuration
There are a couple of different ways to get Spamassassin to do something noticeable. I've used the following configurations:
- As a maildrop filter
- As a relaying filter
I prefer the second method as I found it much more manageable, though it does require another component - a seive rule to deliver emails marked as spam by spamassassin into a different folder, instead of the mailbox. And besides the sieve rule, the LDA needs to be able to operate on it. For that, I would use Postfix and Dovecot, with Postfix setup as the MTA and Dovecot as the LDA.
See Also
- Dspam
- Spamd
Links
- http://koansys.com/tech/sieve-server-side-mail-filtering-with-postfix-dovecot
Spamassassin Links
- Defending against Unsolicited Commercial Email (UCE), also known as Spam - Page 3 - Spamassassin
- Using sa-learn to Teach Spamassassin about the Difference Between Spam and Ham
- Spamassassin and Dspam
- My SpamAssassin Config Files
- Spamassassin Internals
- Spamassassin
- Spamassassin
- Postfix, Dovecot and Spamassassin
- Spamassassin lint - no network tests?
- Spamassassin User Settings