Re: [exim] Content-Scanning $spam_score_int

Page principale
Supprimer ce message
Répondre à ce message
Auteur: W B Hacker
Date:  
À: exim users
Sujet: Re: [exim] Content-Scanning $spam_score_int
Christian Meutes wrote:
> Hello,
>
> what could be the reason that $spam_score is set but $spam_score_int isn't?
>
> acl_check_data:
> ***************
>   warn    message   = X-Spam-Score: $spam_score ($spam_bar)
>           spam      = nobody:true
>   warn    message   = X-Spam-Report: $spam_report
>           spam      = nobody:true

>
>   deny    message   = Classified as spam (score 
> $spam_score)\nX-Spam-Report:$spam_report
>           condition = ${if >{$spam_score_int}{400}{1}{0}}
>           spam      = nobody:true/defer_ok
> ***************

>
> Debug:
> ******
> [...]
> 1873 check spam = nobody:true
> 1873 warn: condition test succeeded
> 1873 processing "deny"
> 1873 check condition = ${if >{$spam_score_int}{400}{1}{0}}
> 1873                 = 0
> 1873 deny: condition test failed
> 1873 processing "accept"
> 1873 accept: condition test succeeded
> 1873 >>Headers added by DATA ACL:
> 1873   X-Spam-Score: 10.3 (++++++++++)
> [...]
> ******

>
> Cheers,
> christian
>


Why do you suppose it is not?

It would appear to have held the value of 103 vs a threshold of 400.

All you need to do to confirm that is to add these lines to your deny
clause:

logwrite = 'Spam Score Int =' $spam_score_int

- which will show up in logs whether the clause is triggeed or not....


optionally:

log_message = 'Rejecting with a Spam Score Int =' $spam_score_int

- which will activate ONLY when (all of) the clause conditional(s) are
satisfied.

You can comment these OFF once you are happy that all is as expected.

HTH,

Bill