Kjetil Paulsen wrote:
seeing the exact problem here from one particular domain, started some
weeks ago...
my server says:
tcpserver: pid 15053 from 89.20.252.149
tcpserver: ok 15053 blue:10.0.0.7:25 <http://10.0.0.7:25>
:89.20.252.149::4609
tcpserver: status: 4/100
the email transcript:
Attempting SMTP connection to [jforce.no <http://jforce.no/>]
Resolving MX records for [jforce.no <http://jforce.no/>] (DNS Server:
89.20.252.130)...
* P=000 S=000 D=jforce.no <http://jforce.no/> TTL=(60) MX=[jforce.no
<http://jforce.no/>] {84.234.141.2}
Attempting SMTP connection to [84.234.141.2:25 <http://84.234.141.2:25/>]
Waiting for socket connection...
Connection established (89.20.252.149:3324
<http://89.20.252.149:3324/> -> 84.234.141.2:25
<http://84.234.141.2:25/>)
Waiting for protocol to start...
* Error: 60 second wait for protocol timeout exceeded
This message is 61 minutes old; it has 0 minutes left in this queue
Remote queue lifetime exceeded; message placed in retry queue
anyone have any suggestions? can't find anything in the logs that
indicate problems :/
On Tue, Nov 3, 2009 at 3:02 AM, jim jackson <[email protected]
<mailto:[email protected]>> wrote:
Hey guys, My server can send mail without any problem and receive
mail from gmail, hotmail, yahoo etc however I'm having trouble
receiving mail from my other domain which is hosted by another
company.
Anyone have advice on how to troubleshoot error: Connected to ip
but connection died. 4.4.2.
I think I remember this popping up a while back when connecting to
MSExchange servers and TLS. It may be resolved by regenerating the TLS
certificate - if it's expired, most MTAs will still use it with just a
warning but some Exchange servers may be configured to deny expired
certificates.
More detailed logging would be helpful though.
