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

Issue Spamassasin marking clean messages

Jllynch

Regular Pleskian
I have some messages that are receiving a very clean score of -100! but getting marked as spam eg ****SPAM****. Note that the score is NEGATIVE, so clean. Can Spamassassin not work with 3 digits negative maybe? Any ideas?

Centos 7 - Plesk Obsidian Version 18.0.26,

From the email header:
X-Spam-Checker-Version: SpamAssassin 3.4.0
X-Spam-Level:
X-Spam-Status: No, score=-100.1 required=4.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,HTML_IMAGE_RATIO_06,HTML_MESSAGE,
LOTS_OF_MONEY,PYZOR_CHECK,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_FAIL,
SPF_HELO_NONE,UNPARSEABLE_RELAY,URIBL_GREY,USER_IN_WHITELIST autolearn=no
autolearn_force=no version=3.4.0

There is no "X-Spam-Report:" on this email but there is on other messages that are real spam.

Thanks.
 
I have some messages that are receiving a very clean score of -100! but getting marked as spam eg ****SPAM****. Note that the score is NEGATIVE, so clean. Can Spamassassin not work with 3 digits negative maybe? Any ideas?

Centos 7 - Plesk Obsidian Version 18.0.26,

From the email header:
X-Spam-Checker-Version: SpamAssassin 3.4.0
X-Spam-Level:
X-Spam-Status: No, score=-100.1 required=4.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,HTML_IMAGE_RATIO_06,HTML_MESSAGE,
LOTS_OF_MONEY,PYZOR_CHECK,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_FAIL,
SPF_HELO_NONE,UNPARSEABLE_RELAY,URIBL_GREY,USER_IN_WHITELIST autolearn=no
autolearn_force=no version=3.4.0

There is no "X-Spam-Report:" on this email but there is on other messages that are real spam.

Thanks.

I would guess that the message gets marked as spam because the SPF failed. As noted in the X-Spam-Status header. Although I am not 100% sure about this.
 
Back
Top