You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@spamassassin.apache.org by da...@chaosreigns.com on 2012/07/01 18:00:09 UTC

Rule updates are too old

SpamAssassin version 3.3.0 has not had a rule update since 2012-06-30.
SpamAssassin version 3.3.1 has not had a rule update since 2012-06-30.
SpamAssassin version 3.3.2 has not had a rule update since 2012-06-30.

20120630:  Spam: 256416, Ham: 219468

Re: Rule updates are too old

Posted by "Kevin A. McGrail" <KM...@PCCC.com>.

On 7/1/2012 3:47 PM, darxus@chaosreigns.com wrote:
> On 07/01, darxus@chaosreigns.com wrote:
>> SpamAssassin version 3.3.0 has not had a rule update since 2012-06-30.
>> SpamAssassin version 3.3.1 has not had a rule update since 2012-06-30.
>> SpamAssassin version 3.3.2 has not had a rule update since 2012-06-30.
>>
>> 20120630:  Spam: 256416, Ham: 219468
> It's true, we missed an update today, and I have no idea why.
>

Looking at logs, you are right.  29th and 1st.

The output from "at" logs email that I give only fires if we do go get 
rules.  Need to figure out what the logic is and add an email about what 
didn't fire.

Re: Rule updates are too old

Posted by da...@chaosreigns.com.

On 07/01, darxus@chaosreigns.com wrote:
> SpamAssassin version 3.3.0 has not had a rule update since 2012-06-30.
> SpamAssassin version 3.3.1 has not had a rule update since 2012-06-30.
> SpamAssassin version 3.3.2 has not had a rule update since 2012-06-30.
> 
> 20120630:  Spam: 256416, Ham: 219468

It's true, we missed an update today, and I have no idea why.

-- 
"Speed is a metaphor for freedom."
http://www.ChaosReigns.com