Daryl C. W. O'Shea wrote, On 24/10/06 8:31 AM: > I don't see any benefit in trying > to be helpful and further complicating how the > trusted/internal networks config works.
In theory that sounds nice, but it violates the principle of least surprise. Consider an ISP that has SpamAssassin working fine using the default for the trust path that includes private network ip addresses in the trusted and internal networks. A user gets a gmail address that is configured to forward to the ISP address. They add the gmail server ip addresses to their trusted_networks in their user_prefs. Now the trusted path is broken because they did not include the private ip addresses in their trusted networks, even though there is no reason for them to be aware of the specifics of the ISP's trusted_networks configuration. To put it another way, a user adding a trusted_network configuration line in user_prefs should not have the side effect of preceding it with an invisible clear_trusted_networks option when the system local.cf is using the default trusted_networks but not when local.cf has an explicit trusted_networks option. Users should not have to know the details of local.cf to configure their own user_prefs. -- sidney
