On 4/8/13 7:18 AM, "Kevin McGrail" <[email protected]> wrote:
> On 4/5/2013 10:08 AM, Jari Fredriksson wrote: >> 05.04.2013 16:19, Kevin A. McGrail kirjoitti: >>> On 4/5/2013 5:00 AM, [email protected] wrote: >>>> SpamAssassin version 3.3.0 has not had a rule update since 2013-03-30. >>>> SpamAssassin version 3.3.1 has not had a rule update since 2013-04-04. >>>> SpamAssassin version 3.3.2 has not had a rule update since 2013-04-04. >>>> >>>> 20130404: Spam or ham is below threshold of 150,000: >>>> http://ruleqa.spamassassin.org/?daterev=20130404 >>>> 20130404: Spam: 22548, Ham: 179579 >>> My guess is some things are wonky over Easter Week for some of the >>> masscheckers and will revisit this soon. >> I don't see some of the masscheckers in ruleqa results, including >> myself. The job runs as normal, no problem seen with it. >> > > I don't use the ruleqa page so I am relying on the masscheck logs. For > example, last night your logs were usable. > > Anyone who is sending logs that doesn't see their's meeting the > requirements? > > Regards, > KAM > Checking corpus/usable-corpus-set1/ham-net-danmcdonald.log for SVN 1465209... > corpus/usable-corpus-set1/ham-net-danmcdonald.log does not meet the > requirements > Checking corpus/usable-corpus-set1/spam-net-danmcdonald.log for SVN 1465209... > corpus/usable-corpus-set1/spam-net-danmcdonald.log does not meet the > requirements So, my mass-checks are in the naughty list. What do I need to do to clean it up? Do I need to purge old entries? Or update my mass-check software? -- Daniel J McDonald, CCIE # 2495, CISSP # 78281
