On Tue, 14 Dec 1999, Steve Haslam wrote:
> bash$ exim -v -M 11xYOT-00014R-00
> delivering message 11xYOT-00014R-00
> LOG: 0 MAIN
> == xxx@??? R=lookuphost defer (-1): host lookup did not complete
> bash$ host -t MX ixl.com
> ixl.com MX 100 mailconn2.ixl.com
> !!! ixl.com MX host mailconn2.ixl.com is not canonical
> ixl.com MX 10 mailconn1.ixl.com
> !!! ixl.com MX host mailconn1.ixl.com is not canonical
> bash$ host -x -t A mailconn2.ixl.com mailconn1.ixl.com
> mailconn2.ixl.com CNAME srvntsxconn2.toc.ixl.com
> srvntsxconn2.toc.ixl.com A 216.99.0.137
> mailconn1.ixl.com CNAME srvntsxconn1.toc.ixl.com
> srvntsxconn1.toc.ixl.com A 216.99.0.136
>
> Hm, will Exim refuse to deliver when an MX points to a CNAME then?
No. It will do the necessary lookups. What it is saying is "host lookup
did not complete". That means some DNS lookup did not complete in a
given time. However, now I get
$exim -bt xxx@???
xxx@???
deliver to xxx@???
router = lookuphost, transport = smtp
host srvntsxconn1.toc.ixl.com [216.99.0.136] MX=10
host srvntsxconn2.toc.ixl.com [216.99.0.137] MX=100
which shows that Exim is handling it OK when the lookups work.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
