On Fri, Oct 07, 2005 at 11:18:11AM -0400, Bowie Bailey wrote:
> The most likely cause is a misconfigured trust path. 3.0.x introduced
> the ALL_TRUSTED rule. This rule is supposed to fire with a negative
> score if the message has not passed through any "untrusted" servers.
> A common problem is that you have not configured your trust path
> properly, so ALL_TRUSTED is firing on spam and lowering the score.
Looks like I was running some version of 3.0 on that machine before
upgrading to Sarge, as pre-upgrade messages do include:
-2.8 ALL_TRUSTED Did not pass through any untrusted hosts
on locally generated messages. Oddly, I no longer see that message
*after* I upgraded to Sarge. But, if anything that would catch more
spam, not less as I'm seeing now.
I've been pushing old spam messages through my new setup to see if how
the scores change. It's starting to look like RBL checks are not
happening any more, but skip_rbl_checks is not adjusted in local.cf.
Ah!
debug: failed to load Net::DNS::Resolver: Can't locate Net/DNS.pm in @INC
I updated two very similar Woody machines that day, and this machine
was trouble -- for some reason dist-upgraded removed a number of
packages for a reason I'm not clear on. (Like Apache and Bind!)
BTW -- Any of these need attention?
$ spamassassin --lint
config: SpamAssassin failed to parse line, skipping: rewrite_subject 0
warning: score set for non-existent rule RCVD_IN_DUL
warning: score set for non-existent rule RCVD_IN_RBL
warning: score set for non-existent rule RCVD_IN_RSS
warning: score set for non-existent rule MICROSOFT_EXECUTABLE
lint: 5 issues detected. please rerun with debug enabled for more information.
--
Bill Moseley
[EMAIL PROTECTED]
