Arch Linux

dan457

Member

Registered: 2014-02-18

Posts: 14

[Solved] Spamassassin 3.4 upgrade borked

Upgraded spamassassin-3.3.2-9-x86_64 to spamassassin-3.4.0-1-x86_64 and then it would not run, borking my postfix install.

Checked .pacnew and nothing has changed in the configuration.

Downgrading to 3.3.2 fixed it for now but was wondering if there is something new that needs to be done to get 3.4 working or if it's just a bad package.

Last edited by dan457 (2014-02-22 03:55:11)

Andreaskem

Member

Registered: 2013-10-13

Posts: 67

Re: [Solved] Spamassassin 3.4 upgrade borked

"...and then it would not run" is not very much to go on. You should probably post some log files and specific error messages if you want somebody to help you.

mychris

Member

From: Munich

Registered: 2012-09-15

Posts: 68

Re: [Solved] Spamassassin 3.4 upgrade borked

Pacman only creates .pacnew files if you have modified the configuration file and there was a change in the configuration file:
https://wiki.archlinux.org/index.php/Pa … save_Files
So you have changed the configuration file and the file in the repos has changed.

I don't know spamassassin, but maybe have a closer look to the config files / error messages / changelog

dan457

Member

Registered: 2014-02-18

Posts: 14

Re: [Solved] Spamassassin 3.4 upgrade borked

True, but as this is a production server, had to get it back up right away and not mess with it for hours.  I have to wait till the weekend before I can take the mail server down long enough for some real troubleshooting.  Was hoping someone else had already been through it.

Andreaskem

Member

Registered: 2013-10-13

Posts: 67

Re: [Solved] Spamassassin 3.4 upgrade borked

So this is a production server that does not have a logging mechanism?

dan457

Member

Registered: 2014-02-18

Posts: 14

Re: [Solved] Spamassassin 3.4 upgrade borked

For spamassassin specificaly no. There was an error when I checked the status manualy, not sure where systemd logs that if at all.  Didn't see anything obvious in /var/log.  As for the exact error, I cannot reproduce it untill I can afford to shutdown the mail service and upgrade spamassassin again.

Just going to leave it for now.  A project for next weekend.

Andreaskem

Member

Registered: 2013-10-13

Posts: 67

Re: [Solved] Spamassassin 3.4 upgrade borked

Systemd should log pretty much everything a service cares to output. A quick look at journalctl as root might just tell you what happened.

djraymondnm

Member

From: Socorro, NM, USA

Registered: 2011-12-28

Posts: 59

Website

Re: [Solved] Spamassassin 3.4 upgrade borked

I also have a problem with spamassassin 3.4.  I don't use the daemon version, but just run my incoming mail through it using procmail.  The symptom is that spamassassin 3.4 passes all mail without adding any messages to the mail header.  Spamassassin 3.3.2 marks up the header, allowing procmail to divert spam to a special mail file.

dan457

Member

Registered: 2014-02-18

Posts: 14

Re: [Solved] Spamassassin 3.4 upgrade borked

I did some reading up on the changes for 3.4.0 and there have been a lot.  Add your issue (different but still significant), and a Debian tester already posting a bug report, I think i'll just stick with 3.3.2 untill the next minor release.  Looks like 3.4 needs a little more time in the oven.  I'll leave the debuging to those that are much better at it than I.

Last edited by dan457 (2014-02-20 06:59:33)

Archonaut

Member

Registered: 2014-02-20

Posts: 7

Re: [Solved] Spamassassin 3.4 upgrade borked

I had the same problem after upgrading to spamassassin 3.4: no spam headers added to emails, thus no spam filtering taking place. This might or might not be the same problem for any of you, but you can give it a try.

Short story: I made it work by running sa-update (as root). At least for me, that fixes it.

Long(er) explanation:
At first, I thought it has something to do with the warning printed during the pacman update. It said "/var/lib/spamassassin is now owned by the spamd user. spamassassin.service will also run under that user. You may need to adjust your setup.", but I guess that applies more for people that run the spamd daemon (I don't) or launch it automatically through systemd. Besides, that directory is owned by spamd:spamd (user:group), but it still has the rx permissions for 'other' so should be fine.

Next thing I noticed 'man spamassassin' mentions that the first attempt to load the 'Default configuration data' is from

/var/lib/spamassassin/3.004000

(notice the 3.004000 which matches the latest version number). That folder contains all the rules used for parsing and detecting spam.
A quick look on my system showed that I didn't have that 3.0004000 folder, but I had the folder corresponding to the previous (major) update version, 3.003002.
That hinted that I could run sa-update (which updates or creates the rules database) for the current version, which will create a new folder. Running '# sa-update' indeed fixed it and now I have X-Spam-xxx headers in mails and everything works smoothly. (read man sa-update just in case if you've never run it before).

So, I don't know if the fact that the rules were not automatically created(downloaded?) for the new version is a package bug or the user is supposed to do that every time when a (major/minor?) spamassassin upgrade happens ... Thinking of it, the 2nd is also sort of a bug: maybe the upgrade process could at least hint/remind you to do that ...

dan457

Member

Registered: 2014-02-18

Posts: 14

Re: [Solved] Spamassassin 3.4 upgrade borked

I did run sa-update.  in my case spammassassin refused to run at all.  I will be trying it again this weekend, and if it does the same I'll post the error before rolling it back to 3.3.2

Maybe I should purge my old config completely first, just to be on the safe side.

dan457

Member

Registered: 2014-02-18

Posts: 14

Re: [Solved] Spamassassin 3.4 upgrade borked

Did the update and ran sa-update and this time it worked.  Didn't kill all my old info, but did remove the non-working /var/lib/spamassassin/3.0004000 folder from before.

If I had to guess, i'd say sa-update somehow failed (fluke?) last time. 

Thanks for the extra info, you pointed me in the right direction when I tested it again.