Logically that's the wrong way - the original guide was always "after 9am UTC" and mine run about 30 minutes after that. Which in summer time (i.e. now) I run at 10:30am local time but still 9:30 UTC. If I moved an hour forward I'd be 9:30 local and 8:30 UTC so before that slot. I can try moving an hour back if anyone wants me to but during winter that will put me an extra hour behind I suspect.
Kevin On 8 Apr 2013, at 13:42, Axb wrote: > On 04/08/2013 02:18 PM, Kevin A. McGrail 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? > > could this have something to do with the daylight saving time changes in some > places (eg: Eurozone) > > I pushed my masscheck slot an hour forward, just in case, but still don't > meet requirements - go figure. >
