Another Bayes question/issue

[Jason Williams]

I've been following the Bayes thread recently and I too have been having
problems with bayes. I just haven't had time to work on it. :/

I'm running FreeBSD 6, with postfix + mailscanner.

I'm going to guess I have a permissions issue, but I get a few odd
things when I run --lint even when specifiying -p to my
spam-assassin.prefs.conf

Here they are:

[97841] warn: config: SpamAssassin failed to parse line,
"/var/spool/MailScanner/spamassassin/" is not valid for "bayes_path",
skipping: bayes_path /var/spool/MailScanner/spamassassin/

Is there a valid "bayes_path"?
Which is followed by:


[97413] dbg: bayes: no dbs present, cannot tie DB R/O:
/root/.spamassassin/bayes_toks
[97413] dbg: config: score set 1 chosen.
[97413] dbg: message: ---- MIME PARSER START ----
[97413] dbg: message: main message type: text/plain
[97413] dbg: message: parsing normal part
[97413] dbg: message: added part, type: text/plain
[97413] dbg: message: ---- MIME PARSER END ----
[97413] dbg: bayes: no dbs present, cannot tie DB R/O:
/root/.spamassassin/bayes_toks


The first line entry is probably causing the above issue.

In my spam.assassin.prefs.conf:

use_bayes 1
bayes_path /var/spool/MailScanner/spamassassin
bayes_file_mode 0770

Here is the contents /var/spool/MailScanner/spamaassasin

ls -la /var/spool/MailScanner/spamassassin/
total 11588
drwxr-xr-x  2 postfix  postfix      512 Aug 30 10:47 .
drwxr-xr-x  5 root     wheel        512 Dec  8  2005 ..
-rw----rw-  1 postfix  postfix     1056 Aug 30 11:04 bayes.mutex
-rw-rw----  1 postfix  postfix    46800 Aug 30 11:07 bayes_journal
-rw-rw----  1 postfix  postfix  2617344 Aug 30 11:04 bayes_seen
-rw-rw----  1 postfix  postfix  2629632 Aug 30 11:04 bayes_toks
-rw-rw----  1 postfix  postfix  3010560 Jul 22 09:34
bayes_toks.expire34434
-rw-rw----  1 postfix  postfix  2908160 Jul 22 09:27
bayes_toks.expire4735
-rw-rw----  1 postfix  postfix  2994176 Jul 22 09:18
bayes_toks.expire71607

So im a little confused here.

I appreciate the help.

-Jason

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.