On 18.09.24 13:42, Grega via users wrote:
Right now in SA 4.0.1 bayes at least for me is really challenging to train and
set up.
I had good trained DB from past V3 install, and it behaved really odd.
I trained it on new set of mails 3000 spam and 3000 ham (HAND PICKED mail it
was PAIN) and I cant get either BAYES_00 or BAYES_99 :)
I mean I get them occasionally, but not even close to what it was in V3.
In V3 SA bayes was decisive, when well trained it was awesome.
Nov in V4.0.1 bayes is NON decisive, and in 90% of cases it gives me BAYES_40
or _50 even after I mark those mails as SPAM OR HAM.
What is even more weird is, that some mails aren`t even bayes scored at all.
BAYES_XX is missing from headers entirely and I
don`t know why...
I`m kind of sorry that I upgraded to 4.0.1...
looking at your first mail, it seems that you only have tokens for a few
days:
dbg: bayes: corpus size: nspam = 1190, nham = 12441 dbg: bayes: DB expiry:
tokens in \
DB: 979401, Expiry max size: 1500000, Oldest atime: 1725361640, Newest atime: \
1725888528, Last expire: 0, Current time: 1725888537
% date -d @1725361640
Tue Sep 3 13:07:20 CEST 2024
% date -d @1725888528
Mon Sep 9 15:28:48 CEST 2024
How do you call spamassassin, directly, via spamass-milter, amavis or other
way?
Did you tune any bayes settings?
Do you have your trusted_networks and internal_networks set up properly?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Spam = (S)tupid (P)eople's (A)dvertising (M)ethod
