• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

/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