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