• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue SpamAssassin not learning... ever

ReneRoth

New Pleskian
Running Plesk for a few years now for my personal mail, and it just seems that the spam filter / SpamAssassin is not learning, at all.
I keep getting the exact same spam messages straight into my inbox over and over and over again, for months now, and always move them to the spam folder by hand. Yet Plesk never learns that those are, in fact, spam. The spam score of those does not increase at all.
How do I go about debugging this behaviour? The `autolearn` header flag stays at `no` for all mails, which seems to indicate that SpamAssassin is not learning from the messages I move by hand?
 
I usually create a rule in /etc/mail/spamassassin/local.cf


Or I create a filter in webmail in which I search for recurring words and move the mail to the spamfolder. This works really well and you don't have to be logged in to webmail.
That absolutely defeats the point of SpamAssassin if I have to do that by hand - at this point I might as well switch to Google Mail and save myself a lot of headaches :(
 
That absolutely defeats the point of SpamAssassin if I have to do that by hand - at this point I might as well switch to Google Mail and save myself a lot of headaches :(
If you thought SpamAssassin has the same capabilities as Google mail in terms of automatic spam recognition you had/have (very) wrong expectations.

Neglecting the fact Google's spam AI is probably much more advanced. It also has millions of mailboxes to learn from. While you may just have a couple of mailboxes on your server?

There are some great Plesk extensions to improve spam filtering. SpamExperts (which can also be used without an extension) or Warden Anti-spam and Virus Protection for example. None of those are free. And perhaps are not as "good" as Google mail. But much better than SpamAssassin with it's default configuration.
 
If you thought SpamAssassin has the same capabilities as Google mail in terms of automatic spam recognition you had/have (very) wrong expectations.
I did not think that for a moment, merely implied that I might be willing to trade off my privacy for better spam protection.
I am also aware Plesk is more interested in upselling, rather than, for example, keeping the SpamAssassin version bundled with their product up to date.
Thank you for your input.

To anyone else coming across this, I recommend:
- manually updating SpamAssassin (this alone makes a huge difference, plesk is around ten years behind)
- updating spamassassin rules from a big aggregator like mailbox.org
- installing the pyzor and razor addons
- adjusting the spam score based on IP geolocation
- training ham from the read mails based on a cronjob
- if you want to go the extra mile, periodically download spam mails and train those too
 
To anyone else coming across this, I recommend:
- manually updating SpamAssassin (this alone makes a huge difference, plesk is around ten years behind)
- updating spamassassin rules from a big aggregator like mailbox.org
- installing the pyzor and razor addons
- adjusting the spam score based on IP geolocation
- training ham from the read mails based on a cronjob
- if you want to go the extra mile, periodically download spam mails and train those too
Those are great suggestions. Thank you for sharing.

I did not think that for a moment, merely implied that I might be willing to trade off my privacy for better spam protection.
I am also aware Plesk is more interested in upselling, rather than, for example, keeping the SpamAssassin version bundled with their product up to date.
Thank you for your input.
With the exception of Windows, Plesk is merely utilizing the SpamAssassin version that comes with the OS. And yes, that is likely to be an older version. Again, Windows being the exception here, on which Plesk does keeps SA updated (sort of).
 
Back
Top