Re: Clarifying internal_networks

2006-06-01 Thread Mark Martinec
On Thursday June 1 2006 04:05, Matt Kettler wrote: Simple rule: trusted_networks - set to cover all machines that might generate a Received: header that you control. internal_networks - Will default to match trusted_networks if not declared. 99% of the time, you just set trusted_networks.

RE: Clarifying internal_networks

2006-06-01 Thread Bowie Bailey
Mark Martinec wrote: On Thursday June 1 2006 04:05, Matt Kettler wrote: Simple rule: trusted_networks - set to cover all machines that might generate a Received: header that you control. internal_networks - Will default to match trusted_networks if not declared. 99% of the time,

Re: Clarifying internal_networks

2006-06-01 Thread Mark Martinec
Bowie, it is imperative than MSA hosts are excluded from internal_networks. What do you do if SA is running on your MSA host? I believe this is the only exception to the rule, because the following probably takes precedence: The machine you're scanning on should be internal trusted

Re: Clarifying internal_networks

2006-05-31 Thread Matt Kettler
Philip Prindeville wrote: I was rereading the sections on trusted_networks and internal_networks in Mail::SpamAssassin::Conf, but something wasn't clear to me. It talks about MXes and relays, but... not about client workstations that might originate email locally and submit it via port 25