• 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 Rules Not Recoginzed

R

rayelder

Guest
According to the Spamassassin website I'v added rules to filter specific vuglar words. Below is the contents of my local.cf file at /etc/mail/spamassassin

required_hits 5
rewrite_subject 1
subject_tag *****SPAM*****
report_safe 0
header L_S_casino Subject =~ /casino/i
score L_S_casino 6.0
describe L_S_casino Subject mentions casino

I've saved the new setting and restarted Spamassassin using "service spamassassin restart". Everything seems to restart properly but when I send a test email with the offensive word in the Subject it doesn't get labeled with *****SPAM*****
 
You must log in or register to reply here.

Similar threads

D
Question SpamAssassin Bayes Training in Plesk: Daily cron disabled by default – bug or by design?
Replies
3
Views
3K
dbmtrde
D
Jürgen_T
Question Migration from Plesk Email Security (Amavis, SpamAssassin 3.x) to Rspamd 3.12 – Experiences?
Replies
16
Views
15K
Claudio.Sp.
C
I
Resolved Preventing bot brute force probes against Postfix/SMTP
Replies
5
Views
921
iainh
I
K
Issue Message is regarded as spam (but isn't spam) and then the spam report is regarded as spam
Replies
3
Views
6K
Kaspar
K
V
Issue Plesk Email Security - Local spamassassin rules not applied
Replies
2
Views
2K
ViaHosting
V
Back
Top