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

2019-07-17 Thread Paul Stead
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/ru

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

2019-07-17 Thread darxus
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

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

2019-07-17 Thread darxus
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.

[auto] bad sandbox rules report

2019-07-17 Thread Rules Report Cron
HTTP get: https://ruleqa.spamassassin.org/1-days-ago?xml=1 HTTP get: https://ruleqa.spamassassin.org/2-days-ago?xml=1 HTTP get: https://ruleqa.spamassassin.org/3-days-ago?xml=1 Bad performing rules, from the past 3 night's mass-checks. (Note: 'net' rules will be listed as 'no hits' unless you set