I can pretty much guarantee that we receive many of these in-the-future emails everyday.
I'll see if I can come up with a way to siphon them off. Do you have any suggestions? Thanks a lot for the information. BTW, what does kluged mean? Was this a typo? Kris -----Original Message----- From: Theo Van Dinter [mailto:[EMAIL PROTECTED] Sent: Thursday, May 27, 2004 12:09 PM To: Kristopher Austin Cc: [EMAIL PROTECTED] Subject: Re: Bayes DB possible problem On Thu, May 27, 2004 at 09:30:24AM -0500, Kristopher Austin wrote: > 0.000 0 1117360742 0 non-token data: newest atime That's in 2005, fyi. > I guess I don't understand what atime is. Is it a numerical form of > when the token was placed in the DB? If so, then why in the world does > it slowly seem to be getting older tokens? Is this the problem? Is > auto-learning using the wrong date/time when adding tokens? It's the numerical time when the message was received (based on a number of different headers). If you dump out the database, you'll probably see a handful of tokens with the atime in the future. If you can find the message that those tokens go with, I'd be very interested in seeing it -- this problem has been reported before, but no one has ever sent me a mail with which I can reproduce the problem. It's kluged around in 3.0 BTW. -- Randomly Generated Tagline: It's easy to solve the halting problem with a shotgun. :-) -- Larry Wall in <[EMAIL PROTECTED]>
