-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Daniel Quinlan writes: > I'd like to make IP_IN_RESERVED_RANGE go away. In an ideal world, but I > know Justin will object so I won't propose it, I would nuke it. Since > it's possible some poor unsuspecting third-party plugin is using it in > the same brokey was as our code was just yesterday, I propose we merely > set it equal to the new IP_PRIVATE constant. > > If you read the comment: > > # Initialize a regexp for reserved IPs, i.e. ones that could be > # used inside a company and be the first or second relay hit by > # a message. Some companies use these internally and translate > # them using a NAT firewall. These are listed in the RBL as invalid > # originators -- which is true, if you receive the mail directly > # from them; however we do not, so we should ignore them. > > That's how it's defined anyway -- an internal address. > > Does that sound okay? +1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFB4yRIMJF5cimLx9ARAkCAAJ9vNTJlev+8pMy3GzxFlQP8lntCDQCfQxVN L9k1HDxGShMVwoitylFZ5jY= =xmiE -----END PGP SIGNATURE-----
