• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • 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.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

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