Robert Felber
Wed, 07 Nov 2007 04:25:55 -0800
On Wed, Nov 07, 2007 at 07:08:44AM -0500, Sahil Tandon wrote: > On Nov 7, 2007, at 3:16 AM, Robert Felber wrote: > > >FROM/MX_MATCHES_NOT_HELO(DOMAIN) for instance is calculated such: > > > >$from_match_regex_verified_helo[0] + > >($total_dnsbl_score/4) + > >($bogus_mx_penalty * $bogus_mx_penalty) + > >$glob_numeric_score > > In the same email that had FROM/MX_MATCHES_NOT_HELO(DOMAIN)=1, there were > three negative DNSBL scores that > summed to -4.5. That sum div by 4 = -1.125 which, No, total_dnsbl_score is the score for dnsbls that have hit. > when added to the 1 score for > $from_match_regex_verified_helo[0], Which you have set to 0 > should've made the aggregate FROM/MX_MATCHES_NOT_HELO(DOMAIN)=-.125, no? > There was no positive bogus_mx_score/penalty on the email. > The only variable I do not understand is > $glob_numeric_score, iwhich may bring the aggregate back to 1. Sorry, was from the devel version, which is $helo_numeric_score[0] * $total_dnsbl_score I don't think FROM/MX_MATCHES_NOT_HELO(DOMAIN)=1 was due to other scores, I explained it rather to not raise wrong assumptions when setting $from_match_regex_verified_helo[0] to 0 (also I haven't seen a log-excerpt, which caused me to make that statement, I can neither say whether it is impossible that FROM/MX_MATCHES_NOT_HELO(DOMAIN) can be "1" if $from_match_regex_verified_helo[0] is set to 0, but I'd guess so). > >However: config changes are picked up by childs after MAINTENANCE_LEVEL > >requests while each child has an own maintenance counter. > >To speed up a complete reloading of all childs use policyd-weight reload. > > That explains it. Thanks for the clarification. > > Sahil > > ____________________________________________________________ > Policyd-weight Mailinglist - http://www.policyd-weight.org/ -- Robert Felber (PGP: 896CF30B) Munich, Germany ____________________________________________________________ Policyd-weight Mailinglist - http://www.policyd-weight.org/