• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

/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