Sidney Markowitz wrote:
Playing around with some mail that I get forwarded from an email address
on one ISP that is aliased to my email address on the ISP from which I
collect it, I noticed that I have to add both the first ISP's mail
servers and 127.0.0.1 to get the trust path do come out right. That has
to do with the peculiarities of the first ISP's setup, but I was
wondering if anyone can think of a reason not to default to having
127.0.0.1 in trusted_networks? The reason for making it the default
would be that it is always the correct setting and if someone encounters
an exception they could clear it using clear_trusted_networks.
Comments, or objections?
It already is a default. If you haven't configured it manually,
anything private is trusted.
use constant IP_PRIVATE => qr{^(?:
10| # 10/8: Private Use (3330)
127| # 127/8: Private Use (localhost)
169\.254| # 169.254/16: Private Use (APIPA)
172\.(?:1[6-9]|2[0-9]|3[01])| # 172.16-172.31/16: Private Use (3330)
192\.168 # 192.168/16: Private Use (3330)
)\.}ox;
If you have configured it manually there shouldn't be any special
defaults. In the vast majority of cases it wouldn't hurt anyone, but
it's also not needed by the large majority of setups. I don't see any
benefit in trying to be helpful and further complicating how the
trusted/internal networks config works.
Daryl
