• 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 Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question Spam detection on outgoing mails with Plesk Email Security

Adarre

New Pleskian
Server operating system version
Ubuntu 22.04.5
Plesk version and microupdate number
Plesk Obsidian 18.0.66 #2
Hi,

How does spam detection on outgoing mails work on Plesk Email Security?

Spam is counted in the stats table. But how are they processed? For me, everything indicates that they are still delivered when a customer account is hacked. How can I make sure they are not delivered? There seems to be no possible setting...

Thanks
 
I tested by sending myself spam-type emails to a second address. When I send myself the GTUBE character string, the email is blocked, I don't even receive it. But for everything else, the emails go through, with fairly low X-Spam-Scores. And yet my tests talk about viagra, money, with lots of red characters and emoji!!

Maybe I should directly modify the spamassassin config, but I'm afraid it will be overwritten by Plesk. In addition, apart from the required_score value, the rest I don't have the skills...
 
As you've already discovered mail is only blocked if the spam score hits the score threshold. You can either lower the mailbox threshold or customize (change, add, remove) any SpamAssassin rules or scores by adding them in separate config files in the /etc/spamassassin directory. Separate config files won't be overwritten by Plesk.

The default SpamAssassin configuration does a pretty poor job at recognizing spam. Adding your own custom spam rules and installing additional plugins (Pyzor, Razor, DCC, Spamhaus DQS to name a few) will improve the ability of SpamAssassin to recognize spam a lot.
 
Back
Top