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

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

HostaHost

Regular 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