Chris wrote:
On Saturday 27 May 2006 12:21 pm, Daryl C. W. O'Shea wrote:
[9324] warn: trusted_networks doesn't contain internal_networks entry
'192.168/16'
[9324] warn: lint: 7 issues detected, please rerun with debug enabled
for more information
Here is my local.cf entry for trusted_networks:
clear_trusted_networks
trusted_networks 127/8
internal_networks 192.168/16
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Isn't this the internal_networks entry?
Yeah, and like the error says, the 192.168/16 network isn't also listed
in trusted_networks like it should be.
Any why did --lint work fine every
time in 3.1.0? Commenting out the internal_networks entry and restarting
SA, --lint shows no errorrs now, why?
We're continuously improving the config parser's ability to detect
configuration *logic* errors. SA 3.1.1 was the first to thoroughly test
the logically configuration of trusted and internal network settings, in
addition to the already present syntactical checking.
If I remember correctly I had setup
my trusted and internal networks the same as I had seen in a message from
JoAnne, I could be wrong though.
It's wrong, trust me. ;)
See http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4760 for a
whole lot of background and insight into this issue.
Like I said before, you need to use at least this (without an
internal_networks line):
trusted_networks 127/8 192.168/16
Additionally, if your MX knows it's public IP you need to add it to the
list of trusted_networks.
If you're using fetchmail to get your Earthlink mail and running it
through SA, you should also add all of the relays through Earthlink's
network (right up to and including their MXes) to your trusted_networks too.
Daryl
