spamassassin-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Maul <jm...@elih.org>
Subject Re: Negative score on spams
Date Wed, 02 Feb 2005 20:45:34 GMT
Matt Kettler wrote:
> At 03:00 PM 2/2/2005, EB wrote:
> 
>> I'm afraid these email might be internal.  Is there a way to "un"
>> trust even if internal network?  The user guide said trusted_networks
>> should be "none" by default, but I think it is not.  Is there a way to
>> "un" trust 127.0.0.1?

If you cant trust your own server, you really shouldnt be running it.

> 
> 
> Heh, what user guide said it was set to "none"? It would be impossible 
> for it to ever be "none". You must have at least one trusted server, 
> otherwise SA will be unable to decide what headers it should apply DUL 
> RBLs to.
> 
> Unless explicitly set, trusted_networks it's set to "auto".
> 
> As far as "un trusting" 127.0.0.1, you REALLY do NOT want to do that 
> because of the implications to whitelists, RBLs, and just about any 
> other part of the code that examines Received: header.
> 
> If your localhost can be a spam relay, disable the ALL_TRUSTED rule by 
> setting it's score to 0.
> 

If your localhost can be a spam relay, fix the problem. Setting 
ALL_TRUSTED to 0 (while fixing the negative score for spam) is not 
really a solution.  It merely masks the problem.

Mime
View raw message