On Sun, Oct 31, 2004 at 09:38:09PM -0200, Juliano Simões wrote: > I have noticed a strange behavior of SA, after upgrading from > version 2.64 to 3.0.1. Sometimes, the same message is scored > with bayes, sometimes not.
Yes, Bayes can't always give an answer. You can run with -D and see what's going on. > See below sample outputs from subsequent executions of > "/usr/bin/spamassassin -tLD < spam_msg_file": Bayes probably learned enough tokens from the first to score on the second. > Version 2.64 was very consistent when it comes to using bayes. > Any clues on what may be causing this problem on 3.0.1? Well, 2.[56]x always gave a BAYES_* hit, even if it wasn't usable (aka BAYES_50). 3.0 only gives you a result when there's a result. -- Randomly Generated Tagline: "It is far more impressive when others discover your good qualities without your help." - Zen Musings
pgpHttE7tBxKi.pgp
Description: PGP signature
