A well-configured spam filter keeps unwanted email out without losing important messages. In Plesk, you manage this through SpamAssassin, which lets you set sensitivity, whitelist, and blacklist per domain or mailbox. This article shows step by step how to enable the filter, fine-tune it, and verify it’s working properly.
How the spam filter works
The spam filter in Plesk runs on SpamAssassin and evaluates incoming email based on characteristics such as sender reputation, content, and technical headers. Each message receives a score; if it exceeds a set threshold, the message is marked as spam or deleted outright. This works alongside standard email security measures like SPF, DKIM, and DMARC, which are already applied with business email.
Setting up the spam filter in Plesk
In Plesk, you’ll find the spam settings under Email > Spam Filter Settings. Here you can set the threshold value that determines from which score a message is considered spam. A lower value filters more strictly but increases the chance of false positives. A higher value lets more borderline cases through.
Open spam settings
In Plesk, go to Email and select the spam filter settings option for the relevant domain or the entire hosting account.
Set the threshold value
Adjust the sensitivity. Start with the default value and only lower it if too much spam gets through.
Choose the action for spam
Decide whether messages are flagged in the subject line, moved to a spam folder, or rejected.
Save and test
Save the settings and send a test message to check that the rules work as expected.
Using whitelist and blacklist
With a whitelist, you ensure that email from trusted senders is never treated as spam, even if the score turns out high. This is useful for suppliers, customers, or internal systems that send automated mail. A blacklist does the opposite: messages from included addresses or domains are always rejected, regardless of content.
Both lists are configured in Plesk under the spam filter settings, either per mailbox or domain-wide. Domain-wide settings are more efficient if multiple mailboxes need to trust or block the same senders.
Dealing with false positives
Sometimes the filter incorrectly marks legitimate mail as spam, or lets actual spam through. In case of a false positive, first check the message headers to see what score was assigned and why. Then adjust the threshold or whitelist instead of disabling the filter entirely.
If a particular sender keeps causing issues, check whether their domain is correctly set up with SPF and DKIM. Missing records are a common cause of incorrect spam flagging. If you’re unsure about the correct configuration of your domain, check the settings under domain names or contact support.
If you’re considering switching to a provider with strong email security and clear spam settings, check out switching to Tandata for the options.
Frequently Asked Questions
Why is spam still arriving in my inbox?
The threshold value may be set too high, or the sender might be missing from the blacklist. Check the spam score in the message headers and adjust the settings.
Can I configure the spam filter per mailbox?
Yes, in Plesk you can configure both domain-wide and individual mailbox settings for whitelist, blacklist, and threshold value.
What should I do if an important message is marked as spam?
Add the sender to the whitelist and check that the threshold isn’t set too strictly.
Does the spam filter affect my own outgoing mail?
No, the filter only evaluates incoming email. For outgoing mail, correct SPF, DKIM, and DMARC configuration is more important.
Where can I find more information about email settings?
The knowledge base contains detailed articles on email configuration and security.
Conclusion
A well-tuned spam filter in Plesk combines an appropriate threshold value with an active whitelist and blacklist. By regularly checking for false positives and adjusting the settings, you keep unwanted mail out while keeping important messages within reach.