From: "Bram Mertens" <[EMAIL PROTECTED]>
> Hi
>
> I ran the following command to test my SA setup:
> [EMAIL PROTECTED]:~> spamassassin -t -D rulesrun=255 < spam.txt >& spam.log4
>
> And the output contains the following:
> debug: using "/usr/share/spamassassin" for default rules dir
> debug: using "/etc/mail/spamassassin" for site rules dir
> debug: using "/home/m8ram/.spamassassin" for user state dir
> debug: using "/home/m8ram/.spamassassin/user_prefs" for user prefs file
> debug: Failed to parse line in SpamAssassin configuration, skipping:
report_header 1
There's no such option of which I am aware.
> debug: Failed to parse line in SpamAssassin configuration, skipping:
defang_mime 0
There's no such option of which I am aware.
> debug: Failed to parse line in SpamAssassin configuration, skipping:
RCVD_IN_BL_SPAMCOP_NET 3.00
Betcha it would not skip "score RCVD_IN_BL_SPAMCOP_NET 3.00" instead.
>
> The first two options (report header and defang_mime) are set in
> /etc/mail/spamassassin/local.cf which was installed when I installed SA
> and haven't been touched since.
>
> The third option is set in ~/.spamassassin/user_prefs:
> RCVD_IN_BL_SPAMCOP_NET 3.00
You left off the "score" from the front of the above line.
> Can anybody tell me what is wrong with these options?
>
> If it matters: I started spamd with 'spamd -d -c -a'.
See comments above. Is this an imported local.cf from a much older version
of spamassassin?
> I also noticed:
> debug: bayes: 18288 tie-ing to DB file R/O
/home/m8ram/.spamassassin/bayes_toks
> debug: bayes: 18288 tie-ing to DB file R/O
/home/m8ram/.spamassassin/bayes_seen
> debug: bayes: found bayes db version 0
> debug: bayes: Not available for scanning, only 0 spam(s) in Bayes DB < 200
> debug: bayes: 18288 untie-ing
> debug: bayes: 18288 untie-ing db_toks
> debug: bayes: 18288 untie-ing db_seen
> debug: Score set 1 chosen.
> debug: Initialising learner
> debug: using "/home/m8ram/.spamassassin" for user state dir
> debug: bayes: 18288 tie-ing to DB file R/O
/home/m8ram/.spamassassin/bayes_toks
> debug: bayes: 18288 tie-ing to DB file R/O
/home/m8ram/.spamassassin/bayes_seen
> debug: bayes: found bayes db version 0
> debug: bayes: Not available for scanning, only 0 spam(s) in Bayes DB < 200
> debug: bayes: 18288 untie-ing
> debug: bayes: 18288 untie-ing db_toks
> debug: bayes: 18288 untie-ing db_seen
>
> So bayes isn't being used? I piped all my mail through sa-learn last
> night using the commands I posted earlier. According to the output SA
> learned from +8000 messages (both ham and spam). What could be wrong
> here?
I hope you fed the ham and spam through on two separate runs. Else you
have to delete the bayes databases and do it over correctly. The
spamassassin faq (wiki) can help you understand this all a little better,
I suspect. It looks for all the world like you fed all "+8000 messages"
on the ham track with none fed through as spam. That WILL leave your
bayes database hosed and useless. If this is indeed what you did then
delete ~/.spamassassin/bayes*. Then start over using the --ham and --spam
options with separated ham and spam mailbox files. In common with all other
software of which I am aware to date spamassassin cannot read your mind for
you when it learns your preferences for ham from spam.
Modulo where you stored the ham and spam, the commands would look something
like this.
sa-learn --ham --showdots --mbox ~/ham
sa-learn --spam --showdots --mbox ~/spam
{^_^}
