Hanno Hecker wrote:
I excluded the check for the RFC 1918 ranges because that server delivers to such a range :) If the check for RFC 1918 and 3330 is included in this plugin, it should have a config file or plugin options with the ranges to check for...
As pointed out, the problem with any patch which mandates the exclusion of specific blocks of IP addresses (based on a reverse name lookup) is that it may be wrong for someone, with the sole exceptions of 127.0.0.0/8, 0.0.0.0/8, and 169.254.0.0/16 (which are all impossible? to be used for e-mail). We could probably even extend that to include 224.0.0.0/4 (multicast) since that should also be unable to be used with a TCP connection like SMTP requires.
All of the blocks mentioned in RCF-3330 as Private-Use or "subject to allocation" should not be hard-coded in the plugin though we could of course have it load a config file to add to any local exclusions (like I don't happen to use 172.16.0.0/12 internally, so I could exclude that block).
Hanno, care to make a second pass to exclude all of the blocks I mention above (in the first paragraph)?
John
