• 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.

Issue Spamassassin & MTA with Mailenable

Michael Neikes

New Pleskian
Sorry for a probably stupid question, but I am lost in regards of SPAM detection :-(

I do use
  • Windows Server 2016
  • Mailenable Enterprise Edition 10.26 and
  • Plesk Obsidian Version 18.0.21 Update #5
For spam detection, I have:
  • enabled in Plesk-Control Panel: Tools&Settings>E-Mail>Spam-> serverwide (checked) incl. adding Text to the subject
  • in MailEnable Management>Messaging Manager>Postoffice>Domain123 settings>Features
    • "Deliver junk email to Junk E- folder" checked
Unfortunately it seems that Spamassassin is not running for every mail coming in.
If so:
  • subject text is added,
  • mail is moved
  • header is updated with
    • X-Spam-Flag: YES
    • X-Spam-Level: ***************
On those which should be marked as Spam and are not I do see at least another entry in the header "X-ME-Content: Deliver-To=Junk", so that I did on top enabled a filter (within Mailenable) where - if this is found in the header - the Mail is marked as spam as well.

I found some articles, that MTA is scanning BEFORE Spamassassin and therefore flags arenot included in header but why isit working sometimes and sometimes not?

Other settings i am not sure/aware about if correct:
  • MailEnable Servers>extensions>Message Filter>SpamAssassin>properties
    • "localhost:738" but test is failing
    • "Bypas..." is enabled
  • Within Plesk and Mailenable the entries for Blacklists are equal

Who can help me out?

Thanks for your help
Michael
 
Ok just a test after all this:
forward an incomed spam to another ailbox -> marked with ****SPAM*** but not moved to spam folder.

seems that complete config is §$%&/
 
Unfortunately, the standard version of MailEnable doesn't have built-in spam filtering. If you're using Plesk Panel, you can take a few precautions through the panel. But that doesn't mean you have no options; it's actually possible to block most spam using DNSBL, EHL Block, and other applications. You can check out my blog post where I explain the settings I use if you'd like: Mail Enable Standart Spam Filtreleme
I've been using these settings for a long time and they're quite successful in both spam and virus protection.
 
Back
Top