mirror of
https://github.com/mjl-/mox.git
synced 2024-12-27 08:53:48 +03:00
17baf9a883
after seeing some junk messages pass the filter, i investigated word counts in junkfilter.db. i had seen suspicious counts that were just around powers of two. did not make sense at the time. more investigating makes it clear: instead of setting new word counts when updating the junk filter, we were adding the new value to the current value (instead of just setting the new value). so the counts got approximately doubled when being updated. users should retrain the junk filter after this update using the "retrain" subcommand. this also adds logging for the hypothetical case where numbers would get decreased below zero (which would wrap around due to uints). and this fixes junk filter tests that were passing wrong parameters to train/untrain... |
||
|---|---|---|
| .. | ||
| bloom.go | ||
| bloom_test.go | ||
| filter.go | ||
| filter_test.go | ||
| parse.go | ||
| parse_test.go | ||