• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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