You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Eddy Beliveau <ed...@hec.ca> on 2010/01/29 17:11:38 UTC

Re: how can i finetune to spamassassin to handle spams (not latest 72_active.cf)

-------- Message original --------
Sujet : Re: how can i finetune to spamassassin to handle spams
De : Bowie Bailey <Bo...@BUC.com>
Pour : users@spamassassin.apache.org
Date : 2010-01-29 09:28
> ram wrote:
>   
>>  
>>
>>     The rules in /usr/share/spamassassin are the original rules from the
>>     install.  If /var/lib/spamassassin/3.002.005 exists, those rules
>>     will be
>>     used instead.  You can verify which rules are being used by
>>     running this
>>     command:
>>
>>        $ spamassassin --lint -D 2>&1 | grep "read file"
>>
>>  
>>  spamassassin --lint -D 2>&1 | grep "read file"
>> [26114] dbg: config: read file /etc/mail/spamassassin/init.pre
>> [26114] dbg: config: read file /etc/mail/spamassassin/v310.pre
>> [26114] dbg: config: read file /etc/mail/spamassassin/v312.pre
>> [26114] dbg: config: read file /etc/mail/spamassassin/v320.pre
>> [26114] dbg: config: read file
>> /var/lib/spamassassin/3.002005/updates_spamassassin_org.cf
>> <http://updates_spamassassin_org.cf>
>> [26114] dbg: config: read file /etc/mail/spamassassin/local.cf
>> <http://local.cf>
>> [26114] dbg: config: read file
>> /var/lib/spamassassin/3.002005/updates_spamassassin_org/10_default_prefs.cf
>> <http://10_default_prefs.cf>
>> [26114] dbg: config: read file
>> /var/lib/spamassassin/3.002005/updates_spamassassin_org/20_advance_fee.cf
>> <http://20_advance_fee.cf>
>>     
> [snip]
>   
>> [26114] dbg: config: read file
>> /var/lib/spamassassin/3.002005/updates_spamassassin_org/72_scores.cf
>> <http://72_scores.cf>
>> [26114] dbg: config: read file
>> /var/lib/spamassassin/3.002005/updates_spamassassin_org/80_additional.cf
>> <http://80_additional.cf>
>>     
>
> So you are running from the updated rules...
>
>   
>>     To see if you have the latest rule, cd to
>>     /var/lib/spamassassin/3.002005/updates_spamassassin_org and do this:
>>
>>        $ grep FH_DATE_PAST_20XX 72_active.cf <http://72_active.cf/>
>>
>>  
>> grep FH_DATE_PAST_20XX 72_active.cf <http://72_active.cf>
>> ##{ FH_DATE_PAST_20XX
>> header   FH_DATE_PAST_20XX      Date =~ /20[2-9][0-9]/ [if-unset: 2006]
>> describe FH_DATE_PAST_20XX      The date is grossly in the future.
>> ##} FH_DATE_PAST_20XX
>>     


Hi!

Interesting subject... which make me checked my 3.3.0 installation

I did update spamassassin to version 3.3.0
Then I erased /var/lib/spamassassin/*
did a "sa-update --verbose"
/Update available for channel updates.spamassassin.org
Update was available, and was downloaded and installed successfully/

cd /var/lib/spamassassin/3.003000/updates_spamassassin_org
grep FH_DATE_PAST_20XX 72_active.cf

and the grep command display nothing !!

Did I missed something ?

Thanks,
Eddy



Re: how can i finetune to spamassassin to handle spams (not latest 72_active.cf)

Posted by Eddy Beliveau <ed...@hec.ca>.
-------- Message original --------
Sujet : Re: how can i finetune to spamassassin to handle spams (not 
latest 72_active.cf)
De : Bowie Bailey <Bo...@BUC.com>
Pour : users@spamassassin.apache.org
Date : 2010-01-29 11:30
> Eddy Beliveau wrote:
>   
>> Hi!
>>
>> Interesting subject... which make me checked my 3.3.0 installation
>>
>> I did update spamassassin to version 3.3.0
>> Then I erased /var/lib/spamassassin/*
>> did a "sa-update --verbose"
>> /Update available for channel updates.spamassassin.org
>> Update was available, and was downloaded and installed successfully/
>>
>> cd /var/lib/spamassassin/3.003000/updates_spamassassin_org
>> grep FH_DATE_PAST_20XX 72_active.cf
>>
>> and the grep command display nothing !!
>>
>> Did I missed something ?
>>     
>
> Well, if you don't have the rule, then you don't have to worry about it
> misfiring!  :)
>   
Hi!

Many thanks for your reply.
> Maybe this rule got replaced with something else in 3.3.0.  I haven't
> updated my systems yet, so I'm not sure.
>   
Yes, it make sense  ;-)

Anyway, I just add this to my local.cf file

header           DATE_ONE_YEAR_FUTURE  
eval:check_for_shifted_date('8760', 'undef')
describe         DATE_ONE_YEAR_FUTURE  Date: is more than a year in 
future after Received: date
lang fr describe DATE_ONE_YEAR_FUTURE  Date: est au moins un an après la 
date de l'en-tête Received:
score            DATE_ONE_YEAR_FUTURE  2.0
score            FH_DATE_PAST_20XX     0.0

this way, I won't have to change it every 10 years

Cheers,
Eddy

-- 
Eddy Beliveau
HEC Montreal
Montreal (Quebec)
Canada


Re: how can i finetune to spamassassin to handle spams (not latest 72_active.cf)

Posted by Bowie Bailey <Bo...@BUC.com>.
Eddy Beliveau wrote:
>
> Hi!
>
> Interesting subject... which make me checked my 3.3.0 installation
>
> I did update spamassassin to version 3.3.0
> Then I erased /var/lib/spamassassin/*
> did a "sa-update --verbose"
> /Update available for channel updates.spamassassin.org
> Update was available, and was downloaded and installed successfully/
>
> cd /var/lib/spamassassin/3.003000/updates_spamassassin_org
> grep FH_DATE_PAST_20XX 72_active.cf
>
> and the grep command display nothing !!
>
> Did I missed something ?

Well, if you don't have the rule, then you don't have to worry about it
misfiring!  :)

Maybe this rule got replaced with something else in 3.3.0.  I haven't
updated my systems yet, so I'm not sure.

-- 
Bowie