On Sat, 30 Oct 2004, Tuc at Beach House wrote:
> > > himinbjorg% sa-learn --dump magic
> > > 0.000 0 3 0 non-token data: bayes db version
> > > 0.000 0 175 0 non-token data: nspam
> > > 0.000 0 73501 0 non-token data: nham
> > > 0.000 0 1027341 0 non-token data: ntokens
> >
> > I think 175 spam messages is not nearly enough for Bayes to be
> > adequately trained. Also, the ratio of ham to spam (~0.3%) looks a
> > bit odd. If it reflects roughly equal time periods over which you
> > received the messages, it suggests you might be missing (or perhaps
> > misclassifying) some of your spam.
> >
> But shouldn't it have carried my database over from my previous install?
> I'd been using it for atleast 6 months on different versions before this
> upgrade. Did it 'forget' it all? Do I need to totally retrain it? I'm
> using a stock install from FreeBSD ports, no local/global overrides.
Looks like somebody didn't read the UPGRADE doc...
Due to the database format change, you will want to do something like
this when upgrading:
- stop running spamassassin/spamd (ie: you don't want it to be running
during the upgrade)
- run "sa-learn --rebuild", this will sync your journal. if you skip
this step, any data from the journal will be lost when the DB is
upgraded.
- upgrade SA to 3.0.0
- run "sa-learn --sync", which will cause the db format to be upgraded.
if you want to see what is going on, you can add the "-D" option.
- test the new database by running some sample mails through
SpamAssassin, and/or at least running "sa-learn --dump" to make sure
the data looks valid.
- start running spamassassin/spamd again
. . . . . . . . . . . . . . .
Randomly generated quote:
"My great concern is not whether you have failed, but whether you
are content with your failure." - Abraham Lincoln
