Nick Howitt wrote:

[root@server ~]# rpm -qa | grep assassin

spamassassin-3.4.0-2.el7.x86_64

Thanks for your quick reply.
I have the same one installed.
Looks like that is the problem and it will get fixed.

[root@server ~]# rpm -qa | grep assassin

spamassassin-3.4.0-2.el7.x86_64

Thanks Nick.

I got the email again today of another failure too. From the url, comment 7, it looks like this will take some time for the fix to work through the processes.

I tried to figure out which version of sa-update we have running but all I get is this:

# sa-update -V

sa-update version svn1475932

  running on Perl version 5.16.3

The error seems to be happening for those on sa-update v3.4.1 and earlier.

If it is any consolation, my update did the same last night and is still doing it this morning. Someone asked a few minutes ago on the bug you linked to when the update would be pushed to the servers.

sa-update does not run through the ClearOS servers. It runs at 04:10 daily through a cron job and downloads directly from spamassassin's servers. You can run it more often manually if you want. I have no idea how quickly updates propagate through the SA servers. From the bug report the fix was pushed 7.5 hours ago.

Nick Howitt wrote:

Try running "sa-update" manually. Spamassassin does not use yum to update.

Thanks Nick. I appreciate your help and guidance.

I ran

sa-update -v

Update available for channel updates.spamassassin.org: 1822491 -> 1822617

http: (curl) GET http://sa-update.spamassassin.org/1822617.tar.gz, success

http: (curl) GET http://sa-update.spamassassin.org/1822617.tar.gz.sha1, success

http: (curl) GET http://sa-update.spamassassin.org/1822617.tar.gz.asc, success

rules: failed to run FORGED_GMAIL_RCVD test, skipping:

	(Can't locate object method "check_for_forged_gmail_received_headers" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 1319) line 227.

)

channel: lint check of update failed, channel failed

Update failed, exiting with code 4

Unfortunately the error messages don't mean anything to me. I'll have to do some Googling.

Ah, found this: Bug report for SpamAssassin Apparently a bug. "This rule was intended only for 3.4.2+ versions" Fix has been made. Not sure how that propagates back to COS and when we get that fix?

Nick Howitt wrote:
P.S. If you're on "COS 7.3 up to date", you're on COS 7.4!

Yes, of course! I had a brain cramp. <grin>

[edit] Another brain cramp. Removed a debug log attachment because it wouldn't allow me to post the message but left the reference in the message. Now deleted as redundant[/edit]

Try running "sa-update" manually. Spamassassin does not use yum to update.

P.S. If you're on "COS 7.3 up to date", you're on COS 7.4!