• Dear Pleskians! The Plesk Forum will be undergoing scheduled maintenance on Monday, 7th of July, at 9:00 AM UTC. The expected maintenance window is 2 hours.
    Thank you in advance for your patience and understanding on the matter.

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