Michael,
> One more 'documentation' issue.
>
> I noticed by looking at code if you have the bounce_killer_score > 20,
> it won't ever call SA (if it thinks its a bounce).
Right.
> This might be good for the 2.6.3 documentation.
I didn't want to make too much fuss about it, thinking that
the exa
> Michael,
>
>
> Oops, an ugly bug introduced with 2.6.2, turning all message IDs into a '1'
> when stored to SQL log. Thanks! Here is a patch:
>
>> (I guess a positive bounce_killer_score in amavisd.conf would TRY to add
>> 100 points to them? Not subtract?)
>
Thanks, got it.. Will be submitt
Michael,
> I guess I am still trying to figure out why small (under the size limit),
> not whitelisted, not exempt, not spam lovers, but is backscatter email is
> getting in with a 'Hits: -,' which means amavisd didn't even look at it.
>
> The only thing I can say for every email that got back in
> Michael,
>
>> documentation says to activate bounce_killer, set score to non zero, and
>> that default is 0, but config file shows 100:
>>
I guess I am still trying to figure out why small (under the size limit),
not whitelisted, not exempt, not spam lovers, but is backscatter email is
getting i
Michael,
> documentation says to activate bounce_killer, set score to non zero, and
> that default is 0, but config file shows 100:
>
> The only user-configurable setting is $bounce_killer_score (also member
> of policy banks), its default value is 0. To activate the bounce killer
> feature, s
documentation says to activate bounce_killer, set score to non zero, and
that default is 0, but config file shows 100:
The only user-configurable setting is $bounce_killer_score (also member
of policy banks), its default value is 0. To activate the bounce killer
feature, set the $bounce_kill
