* on the Tue, Dec 19, 2006 at 02:55:56PM -0000, Gordon McKee wrote:
> Thanks for your ideas but it still doesn't work. I am sure the DNS TTLs
> will have times out by now. On other interesting thing is if I telnet from
> my UNIX box to 123-reg and try to send a message that exim handles the
> domain from I get the following:
<snip 123-reg mx stuff>
It's probably still due to your DNS being broken:
rabies:/var/log/exim4# host -t mx gdmckee.com
gdmckee.com MX 10 mail-1.gdmckee.com
gdmckee.com MX 20 mail-2.gdmckee.com
rabies:/var/log/exim4# host -t ns gdmckee.com
gdmckee.com NS ns1.worldwidedns.net
gdmckee.com NS ns2.worldwidedns.net
gdmckee.com NS ns3.worldwidedns.net
rabies:/var/log/exim4# host mail-1.gdmckee.com ns1.worldwidedns.net
mail-1.gdmckee.com CNAME 82.36.186.17
82.36.186.17 A record currently not present at ns1.worldwidedns.net
rabies:/var/log/exim4# host mail-1.gdmckee.com ns2.worldwidedns.net
mail-1.gdmckee.com CNAME 82.36.186.17
82.36.186.17 A record currently not present at ns2.worldwidedns.net
rabies:/var/log/exim4# host mail-1.gdmckee.com ns3.worldwidedns.net
mail-1.gdmckee.com CNAME 82.36.186.17
82.36.186.17 A record currently not present at ns3.worldwidedns.net
According to all three of your dns servers, mail-1.gdmckee.com is
pointing at three invalid CNAMES now. They should be A records.
123-reg's rejection may be due to that. I can't explain their lack of a
human readable rejection message though.
Mike
