[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Where is spamassassin's bayes database?



Victor Sudakov wrote: 
> Dan Ritter wrote:
> > Victor Sudakov wrote: 
> > > Dear Colleagues,
> > > 
> > > Is anyone running Debian's default SpamAssassin package together with
> > > some MTA (exim, postfix etc)?
> > > 
> > > My question is, when SpamAssassin is accessed over the network
> > > (127.0.0.1:783), where does it keep its Bayesian database? 
> > > 
> > > A command like
> > > spamc -u nobody -L ham  < mail.txt
> > > 
> > > returns that "Message was already un/learned", but for the life of me,
> > > where is the database kept?
> > > 
> > > I've even tried setting bayes_path in local.cf, to no avail. Beats me.
> > 
> > /var/lib/spamassassin/.spamassassin
> > 
> 
> I thought as much, but this directory contains only sa-compile.cache.
> 
> Even if I set "bayes_path /var/lib/spamassassin/.spamassassin/bayes"
> in local.cf, the database does not appear there.
> 

dsr@tao:/var/lib/spamassassin/.spamassassin
$ ls -al
total 29480
drwx------ 3 debian-spamd debian-spamd     4096 Sep 29 10:45 .
drwxr-xr-x 9 debian-spamd debian-spamd     4096 Sep 28 07:33 ..
-rw------- 1 debian-spamd debian-spamd    65280 Sep 29 11:59 bayes_journal
-rw------- 1 debian-spamd debian-spamd 40267776 Sep 27 14:29 bayes_seen
-rw------- 1 debian-spamd debian-spamd  5324800 Sep 29 10:45 bayes_toks
drwxr-xr-x 2 debian-spamd debian-spamd     4096 Sep 25  2018 sa-compile.cache
-rw-r--r-- 1 debian-spamd debian-spamd     1869 Oct 10  2013 user_prefs


dsr@tao:/etc/spamassassin
$ grep -R bayes *
local.cf:# use_bayes 1
local.cf:# bayes_auto_learn 1
local.cf:# bayes_ignore_header X-Bogosity
local.cf:bayes_ignore_header X-Spam-Flag
local.cf:bayes_ignore_header X-Spam-Status
local.cf:#   and a well-trained bayes DB can save running rules, too
v320.pre:# and create a header containing ASN data for bayes
tokenization.


from /etc/default/spamassassin
OPTIONS="--create-prefs --max-children 5 --helper-home-dir --socketpath=/var/lib/spamassassin/socket --port 783 "

That's all I can think of that would be relevant.

-dsr-


Reply to: