• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Spamassassin blacklist fails

MoreThanSixChars

New Pleskian
Hello world,

for quite some time, I have a reproducible issue with Spamassassin:

- Current versions: Spamassasin 3.3.2-2ubuntu1.1 and Plesk 12.0.18 on Ubuntu 12.04.5 LTS (however, the problem has already been present since Plesk 11 and survived all updates until now).

- Spamassassin ist set to tag message as ***SPAM***, and its blacklist contains a number of emails as well as a few blocked domains (like *@myspamdomain.com).

- While most emails from those blacklisted domains are correctly tagged as ***SPAM***, some keep passing the filter without being marked although they come from the same blacklisted domain.

- I have verified that these emails really come from the blacklisted domain (in order to exclude a possible misspelling with similar looking characters).

- The only difference I could find is: The mails that are correctly identified as spam are directly addressed to the receiving email account, whereas the "forgotton" mails are addressed to the original sender, and all other recipients (including the receiving account) are set as BCC.

Can anyone reproduce that blacklisting an entire domain does not work for mails that arrive via BCC (or CC)? Is this a known issue? Or is it just me doing something wrong with the Spamassassin configuration? (I only used the Plesk GUI option to set it up.)
 
Back
Top