You found it!
The IP it's binding to is an alias, which doesn't have direct outbound
access because it's on the amazon EC2 with a NAT'd address... when I tried
to telnet from that IP I couldn't reach yahoo, but when I tried from the
NAT'd address it was ok. The public IP's are NAT'd and assigned as aliases
for licensing on Direct Admin, so Exim was configured to bind to one of them
and it can't directly connect to the internet. Once configured with the
actual IP everything worked ok.
Thanks for everyone who helped!
-----Original Message-----
From: J.R.Haynes [
mailto:J.Haynes@Cranfield.ac.uk]
Sent: Thursday, June 06, 2013 11:38 AM
To: Don O'Neil
Cc: exim-users@???
Subject: Re: [exim] remote_smtp defer (110): Connection timed out on AWS EC2
Instance
On Thu, 6 Jun 2013 at 18:30 +0100, Don O'Neil wrote
> I just tried the extended logging as you suggested, and here's the
> output of the last attempt before it gave up (it tried a whole host of
> yahoo hosts first). I don't see anything in there that is helping me find
the problem.
> What other sorts of issues can cause these types of failures? Any
> other ideas?
Has your machine got multiple interfaces and exim is choosing a different
one from the manual telnet command?
> 17:22:31 8470 Connecting to mta6.am0.yahoodns.net [98.138.112.38]:25
> from
> 54.236.194.225 ... failed: Connection timed out (timeout=5m)
Exim has connected from 54.236.194.225 - is that what you were expecting?
For testing you can force an outbound interface on telnet with -b telnet -b
54.236.194.225 mta6.am0.yahoodns.net smtp
Jonathan
--
-------------------------------------------------------------------
J. R. Haynes
Senior Network Specialist
IT Department, e-mail: J.Haynes@???
Bld 63,
Cranfield University, Tel: Bedford (01234) 754205
Wharley End, Bedford (01234) 750111 Extn 4205
Cranfield, Fax: Bedford (01234) 751814
Beds.,
MK43 0AL.
