Mike Sassaman wrote:
>
> Last but not least I added the line:
> add_header all Report _REPORT_
>
> so that I can see what rules are being hit. Unfortunately I am still
> not seeing these headers added to the messages. The only headers I
> get are these:
>
> X-SMTP-Vilter-Version: 1.1.9
> X-SMTP-Vilter-Spam-Backend: spamd
> X-Spam-Score: 2.0
> X-Spam-Level: **
> X-Spam-Threshold: 4.0
> X-Spam-Probability: 0.5
>
> and in the case of the spam threshold being met:
>
> X-Spam-Status: spam
>
> Before I made the changes to local.cf I deleted my bayes db's so
> everything would be learned afresh.
>
> Despite these changes, most spam continues to receive low scores.
>
> Does anyone have a theory about why I am not seeing the Report
> headers? (I know the local.cf file is being read because when I
> changed the required score from 5 to 4, that change is reflected in
> the headers.)
Those are not normal SpamAssassin headers. I would guess that you've
got another program ("Vilter"?) that calls SA for scoring and then adds
its own headers.
As for the low scores, make sure your network tests are enabled and
working. You may want to feed one of the low scoring spams back through
SA with this command:
spamassassin -D -t < spam.msg
This will produce tons of debugging info. Just scan through it for any
obvious errors. Also keep an eye out for calls to Razor/Pyzor/DCC (if
you are using them) and the blacklists.
The message will be dumped back to the screen at the end with a header
added in showing which rules hit and their scores.
--
Bowie
