On Mon, 16 Apr 2007, Kelson wrote:
Benny Pedersen wrote:
On Sat, April 14, 2007 10:31, Wael Shahin wrote:
whitelist_from 172.16.0.0/16
trusted_networks 172.16.0.0/16
whitelist_from is for email not for ip :-)
That won't do what you think. trusted_networks is for IPs that you trust to
provide honest header information, not IPs that you trust not to send spam.
A more concise definition from the wiki:
http://wiki.apache.org/spamassassin/TrustPath
Trusted Networks
Generally you want trusted_networks set to contain all the mailservers
you control that add Received: headers, and nothing else.
Internal Networks
Set 'internal_networks' to include the hosts that act as MX for your
domains, or that may deliver mail internally in your organisation.
Set 'trusted_networks' to include the same hosts and networks as
'internal_networks', with the addition of some hosts that are
external to your organisation which you trust to not be under the
control of spammers. For example, very high-volume mail relays at
other ISPs, or mailing list servers. Note that it doesn't matter if
the server relays spam to you from other hosts; that still means you
trust the server not to originate spam, which is what
'trusted_networks' specifies.
