http://bugzilla.spamassassin.org/show_bug.cgi?id=3918
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From [EMAIL PROTECTED] 2004-10-24 17:25 -------
Thanks, Theo. I was just concern when I had not seen anything get expired from
my bayes database on both servers for about 8 hours, when I was used to seeing
stuff expired hourly. This is what prompted me to run "sa-learn --force-
expire -D", and seeing the following output made me suspicious that there might
be a problem:
=====
debug: bayes: Can't use estimation method for expiry, something fishy,
calculating optimal atime delta (first pass)
debug: bayes: couldn't find a good delta atime, need more token difference,
skipping expire.
=====
Especially the "something fishy" statement. I see now that my cron job report
will show sync happening each hour, but that expire will only happen if there
are enough tokens to justify it. Anyway, I am closing this erroneous bug
report, all appears to be working fine.
Sorry for the noise!
Bill
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
