Hi,

>   sa-learn --dump magic gives:
>       0.000          0          3          0  non-token data: bayes db version
>       0.000          0      57538          0  non-token data: nspam
>       0.000          0      74876          0  non-token data: nham
>       0.000          0     166338          0  non-token data: ntokens
>       0.000          0 1257478501          0  non-token data: oldest atime
>       0.000          0 1263049426          0  non-token data: newest atime
>       0.000          0 1263049538          0  non-token data: last journal 
> sync atime
>       0.000          0 1263044805          0  non-token data: last expiry 
> atime
>       0.000          0    5529600          0  non-token data: last expire 
> atime delta
>       0.000          0       1868          0  non-token data: last expire 
> reduction count
>
> Your database has 166338 tokens which is larger than the default
> bayes_expiry_max_db_size 150000.  The last expiration ran this morning
> at 8:46.  You could try letting the bayes database get larger and turn
> off bayes_auto_expire.  If you turn off bayes_auto_expire you'll have
> to add something to cron to periodically expire tokens.
> bayes_auto_expire is fine for lower volumes of email, but can get in
> the way with higher volumes.

Can I ask how you calculate the actual time from that number? I
suspect it's the epoch minus some division of 24hrs, but a quick
search wasn't fruitful.

Also, what is the drawback with using auto_expire on larger volumes?
Is it the locking delay and preventing learning new messages during
that time? If you were to put it in cron to manually do an expiry, how
often should it be run?

Is there anything that should be tested prior to making this change,
or is it pretty benign?

I suppose you could take the ntokens value before, and subtract it
from the after value to see how many tokens were expired, right? It
would be interesting to see how many tokens are expired on a regular
basis, but not sure that's very useful, just interesting.

Finally, I opened gmail this evening, and google reported this to me,
which I thought was amusing:

# Webpage display issues: "Aw, Snap!"
http://www.google.com/support/chrome/bin/answer.py?answer=95669&hl=en

Aw, Snap? Isn't that from like 2002?

Totally off-topic comment, but perhaps acceptable for a late Saturday evening.

Thanks very much.
Best regards,
Alex

Reply via email to