X-Spam-Status: Yes, score=4.6 required=3.0 tests=DATE_IN_FUTURE_12_24, DRUGS_ERECTILE,DRUGS_PAIN,FORGED_HOTMAIL_RCVD,MIME_BASE64_TEXT autolearn=no version=3.0.2
note that the ones that were detected scored 4 - lower than the actual default of the recomended 5....
i'd really appreciate any help to make sa detect at least 90% of incoming spam...
first, your Bayes rules don't appear to be hitting. this could be because you haven't trained enough mail. you need minimum 200 ham and 200 spam before they kick in.
second, get the URIBL tests working. they catch an amazing amount of spam. you need a recent version of Net::DNS. try this as root:
perl -MCPAN -e 'install Net::DNS'
i haven't seen a spam on my system in recent memory that didn't hit one or both of bayes + uribl. in today's log file, out of 1068 identified spam messages, BAYES_99 hit 921 and URIBL_* hit 945. those should be your front-line weapons.
save a known spam message to a file like "msg.txt" and then invoke spamassassin on it in debug mode like this:
spamassassin -D --lint msg.txt
look for lines concerning DNS, URIBL, or bayes.
example bayes lines that you want to see:
debug: config: read file /usr/share/spamassassin/23_bayes.cf
debug: bayes: 90539 tie-ing to DB file R/O /home/jsd/.spamassassin/bayes_toks
debug: bayes: 90539 tie-ing to DB file R/O /home/jsd/.spamassassin/bayes_seen
debug: bayes: found bayes db version 3
debug: bayes corpus size: nspam = 9827, nham = 826
note my corpus size - more than 200 each of spam and ham.
example dns/uribl lines:
debug: is Net::DNS::Resolver available? yes
debug: Net::DNS version: 0.39
debug: NS lookup of intel.com succeeded => Dns available (set dns_available to hardcode)
debug: is DNS available? 1
debug: URIDNSBL: domains to query:
-jsd-
