Plesk mailbox protection
Enable SpamAssassin for a mailbox hosted in Plesk, choose a safe handling method and tune it gradually. Start by marking or moving suspected spam so legitimate messages remain recoverable while you assess accuracy.
Enable per mailboxEach hosted address can use its own spam-filter settings.
Quarantine firstMove or mark suspected spam before considering automatic deletion.
Tune graduallyChange sensitivity by one point, then observe it for several days.
Before changing
This guide applies when the address receives mail on a UKC Plesk hosting server. If the domain's MX records point to Microsoft 365, Google Workspace or another provider, configure spam protection there instead.
Check the Spam folder and any existing mail-app rules before changing server filtering. A message can be moved by either layer.
Choose safe handling
Legitimate invoices, enquiries and password messages can be lost without any way to inspect why.
Plesk steps
Sensitivity
Plesk commonly starts with a score of seven. If too much spam reaches the Inbox, reduce the value by one. If legitimate mail is being marked as spam, increase it by one. Wait several days between adjustments so the result is meaningful.
Changing several points at once can produce a dramatic increase in missed spam or false positives.
Sender rules
Add a specific trusted sender to the allow list only when messages are consistently misclassified. Add a persistent unwanted sender to the block list when normal filtering is insufficient. Avoid allowing or blocking an entire domain unless every address under it should receive the same treatment.
Sender addresses can be forged, so an allow-list entry is not a substitute for checking suspicious links, attachments or payment requests.
Improve accuracy
When server training is available, move spam from Inbox to Spam and move legitimate messages from Spam back to Inbox using webmail or an IMAP mail application. Continue reviewing the Spam folder regularly and remember that retention may remove older messages automatically.
Troubleshooting
Need help?
Include the affected mailbox, sender, exact subject, date and time, where the message appeared, current sensitivity and the full message headers or non-delivery response. Do not forward passwords or suspicious attachments.
Important mail still being classified incorrectly?Open a ticket with one recent example and its headers.