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

Repair SpamAssassin

cmaxwell

Regular Pleskian
I upgraded SpamAssassin on an RHEL4 system to the most recent version (3.2.3) and this broke Watchdog system monitoring so I decided to revert back to the original working version of SpamAssassin which was 3.0.6-1.

This broke SpamAssassin as it's not observing the settings for each Plesk user (hit score, etc) - it's just using the defaults.

Can someone advise, what's the way to get it back in sync with the Plesk settings? Should I reinstall psa-spamassassin or something?

Thanks!
 
Your out of luck :(

watchdog is broken with new releases of spamassassin.

If you roll back to a 3.1.x version it will work in watchdog again.

Check art, he keeps all the versions, so pick the latest 3.1.x version.

For me on fc6 its 3.1.8-1.fc6.art

Don't chance running a non watchdog supported spamd!

I find it stops about 3 times a week in general and if watchdog is not monitoring it, it remaiuns stopped until you log in and restart spamd.

If your got a busy server, that means a huge flood of spam!

To roll back the spamd login as root.

Download from art and place it in the directory and cd to that directory

rpm -Uvh --oldpackage nameofpackage.rpm
 
Thanks for your reply.

I actually managed to fix this by downloading the original version of SpamAssassin from up2date:

Code:
up2date --get spamassassin-3.0.6-1.el4

I then installed the RPM with:

Code:
rpm -Uvh --oldpackage spamassassin-3.0.6-1.el4.rpm

Then the last thing I had to do was check the option 'Allow per-user preferences' in Plesk under Server > Spam Filter. This setting had magically reset itself after the reinstall. ;)

All back to normal thankfully!
 
You are safe running up to any 3.1x version of spamassassin without breaking watchdog.

ART has them all archived.
 
Back
Top