> Anything else I can try? How can I verify that SA is reading my
> local.cf? Anyway to enable debugging somewhere?
Yes. "spamassassin -D" at the command line will run SA with debugging and
show you the list of places it is finding rules.
"spamassassin --lint" will check all of the rules for syntax errors. Often
if you have a bad enough errror in a rule, SA will completely give up on the
rest of the file that contained the bad rule. So one bad rule can keep many
other good rules from running. If you had run that after making the
original rule you would have known that it was bad, although not necessarily
what to do to fix it.
"spamassassin -t <myspam" will run SA on a single message and show you the
results of that message. The "myspam" needs to be a text file with the
complete spam message in it, including all of the headers.
Don't forget to restart spamd (if you are running it) after modifying rules.
Loren
