http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4787
------- Additional Comments From [EMAIL PROTECTED] 2006-07-05 18:37 ------- (In reply to comment #7) > I like it overall, I think -- esp if it fixes the problem! -- but: > 1. bayes_min_ham_tokens/bayes_min_spam_tokens -- I'd prefer to leave those out > unless they're needed; bayes_min_ham_tokens/bayes_min_spam_tokens is what fixes this bug to begin with. the token ratio check was just something extra to help the learner learn what we need more of and not what we dont. having bayes_min_(ham|spam)_tokens ensures we dont learn when we dont have enough token data. bayes_min_(ham|spam)_num does not assure us of this, as expiry could knock off alot of the token data and the (ham|spam)_count in bayes_vars does not account for that. i've seen 200+ ham learned where actual ham token count in bayes_token is very small. if you dont do this, and opt just for the token ratio path, then you'd need to have ratio logic in is_scan_available() to skip bayes when the ratio is whacked out... because right now, the ratio logic is only being applied to learn(), in hopes it will help equalize it. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
