Looks like they were done, but not differences in the active.list - https://svn.apache.org/viewvc/spamassassin/trunk/rules/active.list?r1=1863040&r2=1863192&diff_format=h
I assume this is what you refer to - scores seem to have been updated too - https://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/scores/72_scores.cf?r1=1863116&r2=1863187&diff_format=h On Wed, 17 Jul 2019 at 14:51, <[email protected]> wrote: > Can anybody tell why rules didn't get updated today? > > Last few updates: > (year-month-day-hour-minute, SA version, rule version) > > 2019-07-14-01-45 3.3.2 1862963 > 2019-07-14-01-50 3.3.2 1863004 > > 2019-07-15-02-15 3.3.2 1863004 > 2019-07-15-02-20 3.3.2 1863041 > > 2019-07-16-01-20 3.3.2 1863041 > 2019-07-16-01-25 3.3.2 1863075 > > > Over 7 hours later than those last few, with no update today: > 2019-07-17-09-45 3.3.2 1863075 > > Spam and ham are above thresholds. > > On 07/17, [email protected] wrote: > > 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. > > >
