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

Question Sysconfig Spamassassin

Heppi75

Basic Pleskian
Hi, we installed spamassassin version 3.4.4 instead of 3.4.0 on a CentOS 7 machine. All is working fine until we make changes in the plesk admin panel. If we change settings from the spam configuration, plesk is modifying the script /etc/sysconfig/spamassassin and add the --daemonize parameter. This causes that spamassassin is not starting anymore. Could this be prevented?
 
Yes - by no longer using the GUI to make those changes, and making backups of the changes you make, so that if, in the future some plesk repair task or upgrade task overwrites your config, you can copy it back from your backup..

I know it's not ideal, but oh well. Btw, the -d aemonize option should not stop your spamd from starting up?
 
Back
Top