Mageia forum

Last night, an update came through for spamassassin. After the patch, spamassassin no longer worked.

I checked the filter definitions in kmail, and discovered that the rule "spamassassin check" no longer was piping messages through /bin/spamassassin, but now was piping them through /home/jiml/spamassassin.

This, of course, is wrong. I checked other filters that invoke various commands and found that in all cases those commands were listed by full path and pointing to my home directory rather than /bin.

I have made the requisite changes manually, but this obviously is an error in the update.

As a followup on this, spamassassin is now being invoked, but it is not finding any rules. Everything is passing with a spam value of 0.0.

Now I have to find the rules and figure out what has happened...

Perhaps not the cause of your problem, but a necessary update to perl-Net-DNS has not been pushed yet. You can get it from updates_testing:
https://bugs.mageia.org/show_bug.cgi?id=16308

Jim

Check https://bugs.mageia.org/show_bug.cgi?id=16308#c20 - the advisory was missing perl-Net-DNS so this didn't get pushed yet as an update.
You could already install it from core/updates_testing and check if it fixes your issue.

I decided I did not have time to fool with this, so I rolled it back. Did that by moving the directory in the perl environment aside and copying the old version back into place from a backup. Did the same thing with /bin/spamassassin. So now it works again.

Just FWIW you can also use urpmi --dowgrade for that, you only need to specify the version to which you want to downgrade.

perl-Net-DNS was pushed too, you could try again now.