• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

/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