Last night [Fri, 18 Jan 2013 04:30:01 + (GMT)] I got:
channel: SHA1 verification failed, channel failed
Spamassassin rules update failed: error=4
when a cron job attempted to run sa_update. Has anybody else seen this?
Martin
What channels do you update and what version of SpamAssassin?
Regards,
KAM
Martin Gregorie mar...@gregorie.org wrote:
Last night [Fri, 18 Jan 2013 04:30:01 + (GMT)] I got:
channel: SHA1 verification failed, channel failed
Spamassassin rules update failed: error=4
when a cron job attempted
On 1/18/2013 6:24 AM, Martin Gregorie wrote:
On Fri, 2013-01-18 at 05:28 -0500, Kevin A. McGrail wrote:
What channels do you update and what version of SpamAssassin?
SA 3.3.2
sa-update version svn917659
running on Perl version 5.14.3
I'm only using the default rule set.
I'm running
On Fri, 2013-01-18 at 07:02 -0500, Kevin A. McGrail wrote:
On 1/18/2013 6:24 AM, Martin Gregorie wrote:
On Fri, 2013-01-18 at 05:28 -0500, Kevin A. McGrail wrote:
What channels do you update and what version of SpamAssassin?
SA 3.3.2
sa-update version svn917659
running on Perl
On 1/18/2013 8:11 AM, Martin Gregorie wrote:
I edited my cron script (sa_update) to add the -D option to sa-update
and then ran it as ./sa_update 21 | tee sa-diag.txt. File attached.
No update available.
And, of course, this time there was no SHA1 failure: it was obviously a
transient error of
On Fri, 2013-01-18 at 13:04 -0500, Kevin A. McGrail wrote:
If you can keep -D on for a few days or weeks and send in
any errors you get, that would be great.
OK
Martin
