Disabling account spam filtering can help isolate a false-positive problem, but it should be a deliberate temporary or policy decision. Server-level rejection rules and mailbox-specific filters may continue to operate afterward.
IN THIS ARTICLE
What you need before you begin
Record the current filtering settings, engine and affected domain. Review examples of legitimate messages being blocked or moved. If mail is hosted externally, change the settings at the actual mail provider instead of the local DirectAdmin account.
01 Disable account spam filtering in DirectAdmin
- Open E-mail Manager > SpamAssassin Setup or the equivalent spam-settings entry.
- Confirm which account-level filter is enabled. Some DirectAdmin installations use Rspamd behind the available settings.
- Select the disable action and save. Avoid removing unrelated mailbox rules or provider security controls at the same time.
- Send a controlled legitimate message from an external mailbox and compare the result with the earlier failure. Preserve the message headers for diagnosis.
- If this was a test, re-enable the filter with a corrected threshold or targeted rule once the cause is understood. Let users know where to review mail during the test.
How do I check mail handling after disabling the filter?
Confirm the account setting is disabled and determine whether the original delivery problem changed. Check the inbox and spam folders rather than assuming successful SMTP acceptance means normal inbox delivery.
Troubleshoot unexpected results
If messages still fail, inspect bounces, routing, mailbox quota and separate filters. Repeatedly toggling SpamAssassin will not correct an external blacklist or incorrect MX record. If disabling protection creates substantial junk, restore the recorded settings and ask support to investigate specific false positives with full sanitized message headers.