• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

'Modify spam mail subject' server setting not being applied

A

artm

Guest
SpamAssassin server settings not being applied

In the Plesk control panel I have set my own values for Server >> SpamAssassin >> Spam Mail Subject' and the spam theshold. However I am finding that if I create a new mail box for a domain, the values I have set server wide are not being applied to the new mail box. Instead that just gets the old server wide default of *****SPAM***** and a threshold of 7.

A bug, some corruption - or am I missing something?

I see the correct global values in /etc/mail/spamassassin/local.cf. So I wonder where PSA is getting the wrong default value from?
 
I had the same problem and then I noticed that there was another file named:

/etc/mail/spamassassin/local.cf.rpmnew

the syntax of the settings in this file is a little different from my older local.cf:

rewrite_header Subject *****SPAM*****
report_safe 1
required_score 5.0

if you have that file, try putting the new syntax in your local.cf file, restart spamassassin and see if it works.
 
Back
Top