There is no MX record, just a port 25 listener on 64.94.110.11. And the script is just that, a script. It doesn't "accept MAIL FROM and RCPT TO", it just assumes that that is what you're doing and gives the appropriate response for that point in the dialogue.
You will be no doubt pleased to know that there are various patches for the nameservers to treat a positive response of 64.94.110.11 as an NXDOMAIN - got to be a good thing. I also updated my exim configuration to add the above address to the ignore_target_hosts setting, which means that it still treats it as unroutable.
If you're in the UK, this link (http://www.hinterlands.org/ver/txt/) may well be of interest, and there may be some equivalent for you US bods. (the nice thing about it being 0800 is that it costs them money for you to deal with it. (Unfortunately, I doubt that +44800 would work :-( ).
And of course, as if that weren't enough there's also the OpenSSH hole of the day. Oh well, at least that means that Theo's claim is going to have to move from "one" to "two".
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
syntheid
Re: oh my GOD
Date: 2003-09-16 07:36 am (UTC)You will be no doubt pleased to know that there are various patches for the nameservers to treat a positive response of 64.94.110.11 as an NXDOMAIN - got to be a good thing. I also updated my exim configuration to add the above address to the ignore_target_hosts setting, which means that it still treats it as unroutable.
If you're in the UK, this link (http://www.hinterlands.org/ver/txt/) may well be of interest, and there may be some equivalent for you US bods. (the nice thing about it being 0800 is that it costs them money for you to deal with it. (Unfortunately, I doubt that +44800 would work :-( ).
And of course, as if that weren't enough there's also the OpenSSH hole of the day. Oh well, at least that means that Theo's claim is going to have to move from "one" to "two".