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
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 2>&1 | 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
So, I've been keeping an eye on things again today.
Overall, things look pretty good, and most spam is being blocked
outright at the MTA and scored appropriately in SA if not.
I've been inspecting the X-Spam-Status headers for the handful of
messages that do slip through and noticed that most of
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
> >runnin
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 sa-upda
What channels do you update and what version of SpamAssassin?
Regards,
KAM
Martin Gregorie 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 to run sa_upda
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
