On 2011/03/29 11:30, RW wrote:
On Tue, 29 Mar 2011 12:55:51 -0500
Max<mdun...@breakawaysystems.com> wrote:
Heres the output of spamassassin -D --lint:
[29434] dbg: logger: adding facilities: all
[29434] dbg: logger: logging level is DBG
[29434] dbg: generic: SpamAssassin version
Update to the current version. It's not worth giving it any more thought
until you've done that. The rules for 3.2.5 haven't been worked on some
time.
Nuts, 3.2.5 works well enough. Your comment basically tells the world
that it was not the update that caused the problem. It's more like
broken training.
The symptoms sound like somebody did one or more sa-learns with the -ham
and -spam reversed. I ruined my own bayes that way once, long ago. I
simply cleared it out and retrained with my saved corpus after automating
the process so I'd not mess up again.
{^_^}
