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, when added to the 1 score for
$from_match_regex_verified_helo[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, which may bring the aggregate back
to 1.
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/
