no clock problems i know of. I run ntp on all my servers and just double checked to confirm that. All my boxes are in sync to the second.
adam On Tue, 2004-02-10 at 10:53, Matt Kettler wrote: > At 09:31 AM 2/10/2004, Adam Denenberg wrote: > > <snip> > > >[EMAIL PROTECTED] adam]# sa-learn --dump magic > >0.000 0 0 0 non-token data: oldest atime > >0.000 0 1134906269 0 non-token data: newest atime > > > <snip> > > > >debug: bayes: First pass? Current: 1076421753, Last: 1076394691, atime: > >1382400, count: 1019, newdelta: 765, ratio: 1804.70264965653 > >debug: bayes: Can't use estimation method for expiry, something fishy, > >calculating optimal atime delta (first pass) > > The first thing that REALLY jumps out at me, is that your newest token > atime is ahead of the current atime... did you have some kind of massive > clock messup on this system? Theoretically you shouldn't ever have > futuristic tokens.. SpamAssassin isn't a psychic (yet). > > >
