• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

'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