sahostking
Verified User
I decided to revisit SpamAssassin today in light of the recent increase in spam issues, just to evaluate how it performs in comparison.
I installed it via da build, and then configured additional rules using the following:
Additionally, I blocked a known problematic domain (yinoce.com) by adding it to /etc/virtual/blacklist_domains.
I also added the following custom rules to /etc/mail/spamassassin/local.cf:
For RBL blocking, I’m handling that at the Exim level instead of within SpamAssassin. I’m also applying strict scoring for authentication failures (SPF, DKIM, and reverse DNS) using:
/etc/exim.easy_spam_fighter/variables.conf.custom
And for the RBL lists:
/etc/exim.strings.conf.custom
To test effectiveness, I monitored two customer accounts that had been consistently receiving daily spam. Since implementing these changes, both users have reported that they have not received any spam. This is particularly notable given that SpamAssassin is running without greylisting and with minimal customization.
Based on this initial test, SpamAssassin appears to be performing very well out of the box. While Rspamd is often considered more advanced, it seems to require more fine-tuning and symbol configuration to achieve similar results.
I have to admit, the results are somewhat surprising—though it’s possible I’ve simply had a good run so far. I’ll continue monitoring over time to see if this holds up.
I installed it via da build, and then configured additional rules using the following:
Code:
wget https://mcgrail.com/downloads/kam.sa-channels.mcgrail.com.key
sa-update --import kam.sa-channels.mcgrail.com.key
sa-update --gpgkey 24C063D8 --channel kam.sa-channels.mcgrail.com
I also added the following custom rules to /etc/mail/spamassassin/local.cf:
Code:
header HK_GOOGLE_GROUPS exists:X-Google-Group-Id
score HK_GOOGLE_GROUPS 2.5
describe HK_GOOGLE_GROUPS Message sent via Google Groups
dns_server 127.0.0.1
dns_query_restriction deny bl.score.senderscore.com
dns_query_restriction deny sa-trusted.bondedsender.org
dns_query_restriction deny sa-accredit.habeas.com
dns_query_restriction deny zen.spamhaus.org
dns_query_restriction deny multi.uribl.com
score RCVD_IN_ZEN 0
score RCVD_IN_XBL 0
score RCVD_IN_PBL 0
/etc/exim.easy_spam_fighter/variables.conf.custom
Code:
EASY_NO_REVERSE_IP==60
EASY_SPF_FAIL==60
EASY_DKIM_FAIL==60
And for the RBL lists:
/etc/exim.strings.conf.custom
Code:
RBL_DNS_LIST==bl.spamcop.net : mail.bl.blocklist.de : bl.spameatingmonkey.net : bl.mailspike.net : b.barracudacentral.org : multi.surbl.org : black.junkemailfilter.com : truncate.gbudb.net
To test effectiveness, I monitored two customer accounts that had been consistently receiving daily spam. Since implementing these changes, both users have reported that they have not received any spam. This is particularly notable given that SpamAssassin is running without greylisting and with minimal customization.
Based on this initial test, SpamAssassin appears to be performing very well out of the box. While Rspamd is often considered more advanced, it seems to require more fine-tuning and symbol configuration to achieve similar results.
I have to admit, the results are somewhat surprising—though it’s possible I’ve simply had a good run so far. I’ll continue monitoring over time to see if this holds up.
Last edited: