On 06/27, [email protected] wrote: > SpamAssassin version 3.3.0 has not had a rule update since 2012-06-22. > SpamAssassin version 3.3.1 has not had a rule update since 2012-06-22. > SpamAssassin version 3.3.2 has not had a rule update since 2012-06-22. > > 20120627: Spam or ham is below threshold of 150,000: > http://ruleqa.spamassassin.org/?daterev=20120627 > 20120627: Spam: 59326, Ham: 109540 > 20120623: Spam or ham is below threshold of 150,000: > http://ruleqa.spamassassin.org/?daterev=20120623 > 20120623: Spam: 246602, Ham: 119126
Added the requested threshold checking. These are two separate alerts. The rule update check is is based on DNS records, and the threshold checks are based on http://ruleqa.spamassassin.org/ . If either one failes, it'll send an email. If the update check fails, but the threshold checks don't fail, it'll still include the ham / spam counts. If the threshold check fails, but the update check doesn't, it won't mention the last dates of updates. When run on a Saturday, it'll only do one threshold check. When run any other day, it'll check thresholds for the current day, and the last Saturday / net / weekly run, because I believe score generation requires both of them to be above the ham and spam thresholds. -- "theres a lot more to life than chicks none of it matters but theres a lot of it" - LeRoy, #motorcycles, #EFNet, 7/18/06 http://www.ChaosReigns.com
