dbrennecke
asked on
Exchange error -Email not being sent/received
Can someone help diagnose this error? I there anything particular in this message that helps identify why the sender cannot email the recipient? The sender cannot apparently send to anyone at the recipient's domain.
Diagnostic information for administrators:
Generating server: mailhost.XYZisd.org
bsmith@LMNOP.com
#< #5.0.0 smtp; 5.4.7 - Delivery expired (message too old) 'timeout' (delivery attempts: 0)> #SMTP#
Original message headers:
Received: from fisd-hc02.ads.XYZisd.org ([x.x.x.y]) by
mailhost.XYZisd.org with ESMTP; 08 Feb 2009 20:54:37 -0600
Received: from fisd-hc02.ads.XYZisd.org ([x.x.x.y])
by mailhost.XYZisd.org with ESMTP; 08 Feb 2009 20:54:28 -0600
Received: from fisd-mb02.ads.XYZisd.org ([x.x.x.z]) by
fisd-hc02.ads.XYZisd.org ([x.x.x.y]) with mapi; Sun, 8 Feb 2009
20:54:28 -0600
From: "smith, Deanna" <SmithDe@XYZisd.org>
To: "smith, Brad" <bsmith@LMNOP.com>
Date: Sun, 8 Feb 2009 20:54:27 -0600
Subject:
Thread-Index: AQHJimG5SNz22HBX3Em3WVMXPx
Message-ID: <DE683DA100EC7649A8539A131
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative;
boundary="_000_DE683DA100E
MIME-Version: 1.0
Diagnostic information for administrators:
Generating server: mailhost.XYZisd.org
bsmith@LMNOP.com
#< #5.0.0 smtp; 5.4.7 - Delivery expired (message too old) 'timeout' (delivery attempts: 0)> #SMTP#
Original message headers:
Received: from fisd-hc02.ads.XYZisd.org ([x.x.x.y]) by
mailhost.XYZisd.org with ESMTP; 08 Feb 2009 20:54:37 -0600
Received: from fisd-hc02.ads.XYZisd.org ([x.x.x.y])
by mailhost.XYZisd.org with ESMTP; 08 Feb 2009 20:54:28 -0600
Received: from fisd-mb02.ads.XYZisd.org ([x.x.x.z]) by
fisd-hc02.ads.XYZisd.org ([x.x.x.y]) with mapi; Sun, 8 Feb 2009
20:54:28 -0600
From: "smith, Deanna" <SmithDe@XYZisd.org>
To: "smith, Brad" <bsmith@LMNOP.com>
Date: Sun, 8 Feb 2009 20:54:27 -0600
Subject:
Thread-Index: AQHJimG5SNz22HBX3Em3WVMXPx
Message-ID: <DE683DA100EC7649A8539A131
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative;
boundary="_000_DE683DA100E
MIME-Version: 1.0
did you check whether the domain is blacklisted ...www.mxtoolbox.com.
Domains are not blacklisted, only hosts are.
Unfortunately you have mangled too much information to be able to test things correctly. A timeout doesn't really tell you anything. I doubt if it is a blacklisting, because that would normally generate a different type of NDR. The only thing that could be happening is the remote site is blocking all traffic from your network for some reason.
The most likely cause though is a routing issue.
Can you telnet to the remote domain's MX records on port 25?
If not, can you tracert to them and see where the traffic dies?
-M
Unfortunately you have mangled too much information to be able to test things correctly. A timeout doesn't really tell you anything. I doubt if it is a blacklisting, because that would normally generate a different type of NDR. The only thing that could be happening is the remote site is blocking all traffic from your network for some reason.
The most likely cause though is a routing issue.
Can you telnet to the remote domain's MX records on port 25?
If not, can you tracert to them and see where the traffic dies?
-M
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.