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

/etc/mail/spamassassin/local.cf vs KB article 1678

HostaHost

Silver Pleskian
Your article http://kb.parallels.com/en/1678 says:

You can add your own template to /etc/mail/spamassassin/local.cf. As example use the one from /usr/share/spamassassin/10_misc.cf

Yet opening that file on a plesk 11.* server says:

#ATTENTION!
#
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.

So which is it? Safe to modify or DO NOT MODIFY?
 
Looks like it is outdated KB article. The /etc/mail/spamassassin/local.cf stores server-wide filter settings. Template of message can be found in /usr/share/spamassassin/10_default_prefs.cf file.
 
At least on Plesk 11.5 it's safe to modify the file as long as you don't touch settings managed by Plesk, which will be overwritten. AFAIK, these settings include: required_score, rewrite_header, whitelist_from, blacklist_from, unwhitelist_from, unblacklist_from.

So the KB is correct in that sense. However it's a good idea to place customizations in a separate file.
 
Back
Top