Dear DA Team.
# 1
SpamAssassin’s Blacklist & Whitelist don’t work when emails are blocked by ACL checks (ESF / easy_spam_fighter)
For example, if a customer adds an Email address/Domain to their SpamAssassin whitelist/Blacklist ,
it still gets blocked if the email triggers an ESF high-score is drop — so the whitelist/blacklist in SpamAssassin has no effect.
I know it’s possible to disable "EASY_HIGH_SCORE_DROP", but that’s not ideal, because it weakens spam protection (SPF,DKIM,REVERSEDNS) across the board.
The best solution would be for SpamAssassin’s blacklist and whitelist to work together with easy_spam_fighter. That way, web hosting customers can manage their own email filtering rules, without needing the hosting provider to disable ESF or manually ESF should skip checks in /etc/virtual/esf_skip_hosts , esf_skip_senders.
I believe the issue is that in the /etc/exim.conf file, ESF (easy_spam_fighter) runs before SpamAssassin, which means SpamAssassin’s whitelist and blacklist don’t get a chance to take effect when ESF blocks an email.
As a result, even if a sender is whitelisted in SpamAssassin, the email can still be rejected by ESF before SpamAssassin processes it.
# 2
Please add email subject to ESF log.
Reference : https://forum.directadmin.com/threa...essage-its-easy-to-monitor.73027/#post-385268
# /etc/exim.easy_spam_fighter/check_message.conf
Thank you.
------------------------------------
Keyword : SpamAssassin, ESF, Your message to <$recipients> was classified as SPAM. Please add more content, cut down on HTML links, use fewer naughty words etc. Also, ask your IT dept to make sure your mailserver has REVERSEDNS, SPF, DKIM, and is not on any black lists. Your score: xxx
# 1
SpamAssassin’s Blacklist & Whitelist don’t work when emails are blocked by ACL checks (ESF / easy_spam_fighter)
For example, if a customer adds an Email address/Domain to their SpamAssassin whitelist/Blacklist ,
it still gets blocked if the email triggers an ESF high-score is drop — so the whitelist/blacklist in SpamAssassin has no effect.
I know it’s possible to disable "EASY_HIGH_SCORE_DROP", but that’s not ideal, because it weakens spam protection (SPF,DKIM,REVERSEDNS) across the board.
The best solution would be for SpamAssassin’s blacklist and whitelist to work together with easy_spam_fighter. That way, web hosting customers can manage their own email filtering rules, without needing the hosting provider to disable ESF or manually ESF should skip checks in /etc/virtual/esf_skip_hosts , esf_skip_senders.
I believe the issue is that in the /etc/exim.conf file, ESF (easy_spam_fighter) runs before SpamAssassin, which means SpamAssassin’s whitelist and blacklist don’t get a chance to take effect when ESF blocks an email.
As a result, even if a sender is whitelisted in SpamAssassin, the email can still be rejected by ESF before SpamAssassin processes it.
# 2
Please add email subject to ESF log.
Reference : https://forum.directadmin.com/threa...essage-its-easy-to-monitor.73027/#post-385268
# /etc/exim.easy_spam_fighter/check_message.conf
# /etc/exim.clamav.conf
Thank you.
------------------------------------
Keyword : SpamAssassin, ESF, Your message to <$recipients> was classified as SPAM. Please add more content, cut down on HTML links, use fewer naughty words etc. Also, ask your IT dept to make sure your mailserver has REVERSEDNS, SPF, DKIM, and is not on any black lists. Your score: xxx