http://bugzilla.spamassassin.org/show_bug.cgi?id=4058
------- Additional Comments From [EMAIL PROTECTED] 2005-05-03 15:42 ------- Suggestion to improve things. Really, this bug occurs mostly because there are two algorithms for inferring trust when private/reserved IPs exist. 1) Trust all reserved IPs, plus first non-reserved. 2) Trust all reserved IPs, first non-reserved untrusted. Algorithm 1) works if your outer-most MX has a non-reserved IP, and fails with over-trust if your outer-most MX is using some kind of static-mapped NAT or other mechanism that gives it a reserved IP. Algorithm 2) works if you have a NATed MX, but fails with under-trust if your MX is not NATed. Why not add a config option that will control if SA assumes the MX is NATed or not? i.e. trusted_networks_nated_mx (default disabled) This would at least make it easy for people to fix, and obvious in the manpage they might want to consider it. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
