On Mon, May 15, 2006 at 09:05:44AM +0200, Michael Monnerie wrote: > bayes: synced databases from journal in 4 seconds: 1690 unique entries > (3283 total entries) > expired old bayes database entries in 180 seconds > 209328 entries kept, 1347841 deleted > > It should keep 2m settings, but kept only 209k. Is there a way to see > which settings SA actually uses? In postfix there's a "postconf -n", > which is very practical, but > spamassassin -D --lint 2>&1|less > doesn't show me that.
No, there is no way to see that. You can see which files are being read, and
assuming there are no conf errors, all of the options should be used.
Unfortunately, the output doesn't actually give enough details to figure
out what happened, but here's a theory:
Since 209328+1347841 < 2000000, an expire wouldn't have been attempted
opportunistically. However, running "sa-learn --force-expire" would
have made it happen. 209328+1347841 = 1557169. Bayes will try to expire
tokens down to 75% of the max number. So 2000000*0.75 = 1500000, which
means it saw that it should try to expire 1557169-1500000 = 57169 tokens.
If the previous expire looks similar to this expire run, Bayes will
use an estimate for atime to do the expire. This speeds things up,
but also could possibly be wrong (it is an estimate afterall). So if
an estimate was used, up to 1557169-100000 tokens (100k is a safety net)
could be expired.
--
Randomly Generated Tagline:
"What the hell is this? For crying out loud, somebody throw a pie!"
- Peter Griffin on Family Guy
pgp9Mr47SXo1K.pgp
Description: PGP signature
