Theo Van Dinter wrote on Sun, 13 Jul 2008 12:24:29 -0400: > This means there weren't enough tokens in the message.
Thanks, Theo, for the quick answer. Ok, false alarm? I used a real message and now I get Bayes and a score. BUT: I ran the lint under 3.2.4 on two different machines. The first shows that warning and the other doesn't. I also get BAYES_50 on the second and no BAYES on the first. Shouldn't this be the same on both? And a second problem on the other machine: While troubleshooting I found that I should expire the db on the second machine as it contained over 3 million tokens. That's the result: [18595] dbg: bayes: expiry starting [18595] dbg: locker: refresh_lock: refresh /home/spamd/bayes/bayes.mutex [18595] dbg: locker: refresh_lock: refresh /home/spamd/bayes/bayes.mutex [18595] dbg: bayes: expiry check keep size, 0.75 * max: 1125000 [18595] dbg: bayes: token count: 0, final goal reduction size: -1125000 [18595] dbg: bayes: reduction goal of -1125000 is under 1,000 tokens, skipping expire [18595] dbg: bayes: expiry completed Makes no sense to me. 0.000 0 3 0 non-token data: bayes db version 0.000 0 60887 0 non-token data: nspam 0.000 0 241224 0 non-token data: nham 0.000 0 3548687 0 non-token data: ntokens 0.000 0 1136505669 0 non-token data: oldest atime 0.000 0 1215939142 0 non-token data: newest atime 0.000 0 1215939367 0 non-token data: last journal sync atime 0.000 0 1147637887 0 non-token data: last expiry atime 0.000 0 11059200 0 non-token data: last expire atime delta 0.000 0 1206279 0 non-token data: last expire reduction count Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com
