hi

I use sa-update with channels      and updates.spamassassin.org.

After the latest run today I am getting matches against BAYES_99
(which adds 3.5) to many messages, where they previously triggered
virtually no rules at all.

This is causing many false positives, to the extent that I've had to
set the score to zero to avoid them.

Anyone else seeing this? Better, have the rule or rules that are
causing this been identified (and fixed)?

Else, if the bayes db has been damaged by something, how do I remove
whatever is persuading it about the high probability this rule indicates?

Well, the sa-update itself wouldn't change the behavior of BAYES_99
unless there was a grossly stupid or malicious error made by the
maintainers. All sa-update could do is change the rule, which amounts to:

body BAYES_99               eval:check_bayes('0.99', '1.00')

Thanks.  Yes that is how I reasoned it too.

*however* an updated ruleset might change the behavior of your
auto-learning, by increasing spam scores with rule hits. You might want
to go digging through your logs and see if there's a lot more spam
autolearning going on post-upgrade. That said, I'd expect that to make
a change over a period of a few weeks, not instantly.

Agreed and a quick look through the logs showed that bayes_99 was listed in all reports over the last day, but virtually non existent for a week or so before that. which pointed to some amiss by dint of upgrade.

Perhaps your bayes DB is merely just not well trained and this is a
problem that's been building but went unnoticed so far? What's a
"sa-learn --dump magic" output look like?

# sa-learn --dump magic
0.000          0          3          0  non-token data: bayes db version
0.000          0        297          0  non-token data: nspam
0.000          0     982365          0  non-token data: nham
0.000          0     160628          0  non-token data: ntokens
0.000          0 1195344836          0  non-token data: oldest atime
0.000          0 1195532636          0  non-token data: newest atime
0.000 0 1195532327 0 non-token data: last journal sync atime 0.000 0 1195517625 0 non-token data: last expiry atime 0.000 0 172800 0 non-token data: last expire atime delta 0.000 0 72520 0 non-token data: last expire reduction count

Thoughts?

many thanks

rolf.


This message may contain confidential information which is intended only for 
the individual named.
If you are not the named addressee you should not disseminate, distribute or 
copy this email.
Please notify the sender immediately by email if you have received this email 
by mistake and delete this email from your system.
Email transmission cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses.
The sender therefore does not accept liability for any errors or omissions
in the contents of this message which arise as a result of email transmission.
If verification is required please request a hard copy version.

Reply via email to