Facebook
TwitterHi, 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?
-
Inviting everyone who uses WordPress management tools in Plesk
The Plesk team is conducting a 60-minute research session that includes an interview and a moderated usability test.
To participate, please use this link .
Your experience will help shape product decisions and ensure the tools better support real-world use cases.
Question Sysconfig Spamassassin
- Thread starter Heppi75
- Start date
tkalfaoglu
Silver Pleskian
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?
I know it's not ideal, but oh well. Btw, the -d aemonize option should not stop your spamd from starting up?
Similar threads
