> -----Original Message----- > From: Matt Kettler [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 15, 2005 9:32 AM > To: Dallas L. Engelken > Cc: spamassassin-users@incubator.apache.org > Subject: Re: Messages without received headers and ALL_TRUSTED > > Dallas L. Engelken wrote: > > score ALL_TRUSTED 0 > > > > Is what I do in local.cf... > > > > I'd not recommend that practice. ALL_TRUSTED misfires are at > least a good warning flare that there's problems. >
I didn't recommend it, I just said that's what "I do" ;) > If the problem is a trust path issue, then that's your > warning to fix it. > True. But in my case, my trusted paths never see SA because of Host Access rules that determine which scanners to pass mail through. So by doing it at the MTA level, I'm saving a few CPUs by not walking through the Received: headers and checking the trusts. :0) > If the problem is header-parsing, that should be fixed in > 3.1.0 so it at least doesn't fire off ALL_TRUSTED when > there's an unparsable header. > > I'd consider at least keeping it in at -0.01 to remind > yourself you've got problems to fix. > I agree with your recommendation of -0.01 vs disabling ALL_TRUSTED as a temporary solution. D
