You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sysadmins@spamassassin.apache.org by "Kevin A. McGrail" <km...@apache.org> on 2019/07/17 11:33:09 UTC
Fwd: Rule updates are too old - 2019-07-17 3.3.0:2019-07-16
3.3.1:2019-07-16 3.3.2:2019-07-16
Is this accurate? I thought we promoted and all looks ok but sometimes my
eyesight is bad so maybe a digit is off.
Can someone please confirm we promoted a set?
---------- Forwarded message ---------
From: <da...@chaosreigns.com>
Date: Wed, Jul 17, 2019, 07:00
Subject: Rule updates are too old - 2019-07-17 3.3.0:2019-07-16
3.3.1:2019-07-16 3.3.2:2019-07-16
To: <da...@chaosreigns.com>, <de...@spamassassin.apache.org>
SpamAssassin version 3.3.0 has not had a rule update since 2019-07-16.
SpamAssassin version 3.3.1 has not had a rule update since 2019-07-16.
SpamAssassin version 3.3.2 has not had a rule update since 2019-07-16.
20190716: Spam and ham are above threshold of 150,000:
http://ruleqa.spamassassin.org/?daterev=20190716
20190716: Spam: 909844, Ham: 452769
The spam and ham counts on which this script alerts are from
http://ruleqa.spamassassin.org/?daterev=20190716
Click "(source details)" (it's tiny and low contrast).
It's from the second and third columns of the line that ends with
"(all messages)"
The source to this script is
http://www.chaosreigns.com/sa/update-version-mon.pl
It looks like both the weekly and nightly masschecks need to have sufficient
corpora in order for an update to be generated.
Re: Rule updates are too old - 2019-07-17 3.3.0:2019-07-16
3.3.1:2019-07-16 3.3.2:2019-07-16
Posted by Bill Cole <sa...@billmail.scconsult.com>.
On 17 Jul 2019, at 7:33, Kevin A. McGrail wrote:
> Is this accurate?
It appears to be, from a user perspective.
> I thought we promoted and all looks ok but sometimes my
> eyesight is bad so maybe a digit is off.
>
> Can someone please confirm we promoted a set?
There has been no rule update available so far this morning. Typically
one is available around 0900 UTC.
>
> ---------- Forwarded message ---------
> From: <da...@chaosreigns.com>
> Date: Wed, Jul 17, 2019, 07:00
> Subject: Rule updates are too old - 2019-07-17 3.3.0:2019-07-16
> 3.3.1:2019-07-16 3.3.2:2019-07-16
> To: <da...@chaosreigns.com>, <de...@spamassassin.apache.org>
>
>
> SpamAssassin version 3.3.0 has not had a rule update since 2019-07-16.
> SpamAssassin version 3.3.1 has not had a rule update since 2019-07-16.
> SpamAssassin version 3.3.2 has not had a rule update since 2019-07-16.
>
> 20190716: Spam and ham are above threshold of 150,000:
> http://ruleqa.spamassassin.org/?daterev=20190716
> 20190716: Spam: 909844, Ham: 452769
>
>
> The spam and ham counts on which this script alerts are from
> http://ruleqa.spamassassin.org/?daterev=20190716
> Click "(source details)" (it's tiny and low contrast).
> It's from the second and third columns of the line that ends with
> "(all messages)"
>
> The source to this script is
> http://www.chaosreigns.com/sa/update-version-mon.pl
>
> It looks like both the weekly and nightly masschecks need to have
> sufficient
> corpora in order for an update to be generated.
--
Bill Cole
bill@scconsult.com or billcole@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)