Search your drive for stray copies of local.cf. See if you ended up with an
etc/spamassassin directory or have a local.cf in your home directory.
RO
----- Original Message -----
From: "Christopher Scott" <[EMAIL PROTECTED]>
To: <users@spamassassin.apache.org>
Sent: Tuesday, August 16, 2005 11:30 AM
Subject: Re: question re. SA setup
On Aug 16, 2005, at 1:51 PM, Kevin Peuhkurinen wrote:
Christopher Scott wrote:
<snip>
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH (0x8430ec8)
implements 'parse_config'
debug: plugin: Mail::SpamAssassin::Plugin::Hashcash=HASH (0x8e687ec)
implements 'parse_config'
config: SpamAssassin failed to parse line, skipping: rewrite_subject 1
config: SpamAssassin failed to parse line, skipping: subject_tag
[***SPAM***]
config: SpamAssassin failed to parse line, skipping: auto_learn
1
config: SpamAssassin failed to parse line, skipping: report_header 1
config: SpamAssassin failed to parse line, skipping: rewrite_subject
1
config: SpamAssassin failed to parse line, skipping: subject_tag
[***SPAM***]
config: SpamAssassin failed to parse line, skipping: use_terse_report
0
config: SpamAssassin failed to parse line, skipping: report_header
1
config: SpamAssassin failed to parse line, skipping: auto_learn
1
debug: using "/root/.spamassassin" for user state dir
debug: bayes: 8624 tie-ing to DB file R/O /root/.spamassassin/
bayes_toks
debug: bayes: 8624 tie-ing to DB file R/O /root/.spamassassin/
bayes_seen
debug: bayes: found bayes db version 3
debug: using "/root/.spamassassin" for user state dir
debug: bayes: Not available for scanning, only 33 spam(s) in Bayes DB
< 200
</snip>
You appear to be running SA 3.04 but using a config file with older and
obsolete directives. This is likely the root of all of your problems.
For instance, instead of "auto_learn 1", the line should be
"bayes_auto_learn 1", which is the directive that allows SA to auto
train the Bayesian database.
Take a look at the documentation on configuring SA (http://
spamassassin.apache.org/full/3.0.x/dist/doc/ Mail_SpamAssassin_Conf.html)
and spend some time making sure that your local.cf file uses the proper
syntax. This should hopefully solve your problems.
Kevin
This makes sense, as I installed SA3 on top of a previous version.
However, I've edited /etc/mail/spamassassin/local.cf to contain the
following (minus comments):
whitelist_from [EMAIL PROTECTED]
required_score 5
rewrite_header subject [***SPAM***]
use_bayes 1
bayes_auto_learn 1
use_razor2 1
use_dcc 1
use_pyzor 1
dns_available yes
and restarted the service, yet spamassassin --lint -D returns identical
results as before! Could there be another local.cf file somewhere?!
