A domain filter can block mail associated with multiple addresses at the same domain. Its broad scope makes it useful for a consistently unwanted source, but risky when the domain also belongs to customers, suppliers or a public mail provider.
IN THIS ARTICLE
What you need before you begin
Confirm the intended domain and the scope of the DirectAdmin filters for your account. Review legitimate correspondence before blocking the whole domain. A forged sender domain can appear in spam, so inspect examples rather than trusting a display name.
01 Block a sender domain with DirectAdmin email filters
- Open E-mail Manager > SPAM Filters for the correct domain context.
- Choose the Domain match type.
- Enter only the sender domain, such as
example.com, without a protocol, path or unnecessary www prefix. - Review the action applied to matches and add the rule. Use a reviewable destination during evaluation when your installation provides one.
- Monitor incoming mail and confirm the intended scope, including how the implementation handles subdomains. Do not assume every matching rule treats parent and child domains identically.
How do I test the sender-domain filter?
Check that the unwanted source is filtered and that important business mail still arrives. Review filtered mail and any delivery complaints from users affected by the domain-wide rule.
Troubleshoot unexpected results
If a legitimate sender is blocked, remove or narrow the rule and test again. Blocking a large public email provider can exclude many unrelated people, so prefer a precise sender rule or scored spam filtering where suitable. If spam forges changing domains, repeatedly expanding the block list may create more false positives without fixing the underlying pattern.