Facebook
Twitter
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?
-
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
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
