Hungry Snail wrote:
Hi Guys,
I just ran
sa-learn --spam --configpath=/etc/mail/spamassassin/ --showdots
/var/vmail/mydomain/myaccount/.NOT-HAM/cur/
First, stop using --configpath. That option over-rides where the default
ruleset lives. You don't need this option unless you are a developer, or
are doing something quite advanced like running multiple SA instances
with different base rulesets.
/etc/mail/spamassassin should be your --siteconfigpath, not
--configpath. However, SA should properly auto-detect this on its own.
and it reported the following.
Learned tokens from 290 message(s) (305 message(s) examined)
however, when I run 'sa-learn --dump magic' it reports exactly the same
numbers as before I ran the sa-learn.
0.000 0 3 0 non-token data: bayes db version
0.000 0 181508 0 non-token data: nspam
0.000 0 30468 0 non-token data: nham
0.000 0 160708 0 non-token data: ntokens
0.000 0 1208248441 0 non-token data: oldest atime
0.000 0 1217700458 0 non-token data: newest atime
0.000 0 1210512752 0 non-token data: last journal sync
atime
0.000 0 1217698387 0 non-token data: last expiry atime
0.000 0 1382400 0 non-token data: last expire atime
delta
0.000 0 58981 0 non-token data: last expire
reduction count
Any ideas why?
That seems really odd to me. However, does it change when you run:
sa-learn --configpath /etc/mail/spamassassin/ --dump magic
Basically I'm wondering if the forced configpath is making one sa-learn
instance use a different bayes path than the other.
