On Thu, 28 Jul 2005 09:38:14 -0400
Keith Ivey <[EMAIL PROTECTED]> wrote:
> Hanno Hecker wrote:
> > we had some (smaller) troubles with a spammer sending mails with a
> > resolvable MX, but that MX pointed to 127.0.0.1... after
> > blacklisting these sending IP for a short time I added a check to
> > the require_resolvable_fromhost plugin...
>
> I used to have my require_resolvable_fromhost patched to check for
> 127.* as well as the private-use ranges (RFC 1918):
>
> 10.0.0.0 - 10.255.255.255
> 172.16.0.0 - 172.31.255.255
> 192.168.0.0 - 192.168.255.255
>
> and the autoconfiguration range (RFC 3330):
>
> 169.254.0.0 - 169.254.255.255
> Does anyone else think these checks should be added to the standard
> plugin? It's all very well for an address to be resolvable, but if it
>
> resolves to an IP address that makes it impossible to deliver it's not
>
> much different from not resolving at all.
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...
Hanno
