On this page
You should almost never disable SpamAssassin on a LogicWeb cPanel account. Leave it running, whitelist trusted senders, and adjust the score only when a real message keeps landing in junk. Turning the whole filter off because one invoice was marked spam is how the rest of the mailbox fills with junk.
How SpamAssassin scores mail
Every inbound message receives a numeric score based on headers, content, and known spam patterns. In cPanel under Spam Filters you set the required hits value and choose whether high-scoring mail is deleted or filed into the spam folder. The default threshold is a workable middle ground for most accounts. If a known customer lands in junk, add a whitelist for that address rather than lowering the score for everyone. If the spam folder is overflowing, raise the threshold slightly and check whether a catch-all address is feeding extra noise into the account.
Whitelist and filters before you turn anything off
Whitelist your own domains and regular business contacts so internal mail is not punished for ordinary words or short links. Roundcube filters using Sieve run after SpamAssassin on this stack, so you can still file by sender, header, or the spam flag. Prefer those rules over a global disable. One client who needs a whitelist does not mean the whole domain should stop scoring mail.
What disabling SpamAssassin actually does
In cPanel → Spam Filters, turning SpamAssassin off means this layer no longer scores mail, auto-deletes high hits, or files messages into spam. It does not stop Gmail or other providers from junking your outbound mail. It also does not disable other server-side protections. It only means the mailbox accepts more unfiltered junk locally, and you often end up building folder rules that work worse than the original score.
The practical default is simple. Leave SpamAssassin on, whitelist yourself and your accounting contacts, and use Sieve for special cases. Auto-delete at a high score is fine if you watch the spam folder for a week. Use off only for a short debug session, then turn it back on. If you disabled it months ago and the inbox is unusable, restore a moderate required-hits value, whitelist the two senders who complained, and empty the spam folder once so you can see what the filter is catching. SpamAssassin does not fix outbound delivery problems; those still depend on SPF, DKIM, and clean message templates.
Tagged
Was this article helpful?
Be the first to rate this article.
