I have some questions about SpamAssassin's relationship to Easy Spam Fighter (ESF) and DirectAdmin's built-in spam filtering tools. According to the ESF docs, SpamAssassin is only called if ESF's spam score is below the EASY_LIMIT value. (At least I think that's how it works. The actual definition of EASY_LIMIT is poorly written and ambiguous: 'max score before an email is considered spam before SA is rung'. ?)
So, this raises some questions:
So, this raises some questions:
- If a message is considered spam by ESF, but SpamAssassin is never called, what happens to the client's custom SpamAssassin rules (including Blocklist and Allow)? Are they completely ignored?
- DirectAdmin offers its own ability to blacklist email addresses under E-mail Manager > SPAM Filters (E-mail Filters). If there's a risk that SpamAssassin is never called, would you recommend that your clients use this feature in preference to the Blocklist feature in SpamAssassin?
- When using DirectAdmin to block an email address, does it block the envelope-from (or return-path) address, or does it block the visible from address, or both? (Is it the same with SpamAssassin?)