We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now


Exchange error -Email not being sent/received

dbrennecke asked
Medium Priority
Last Modified: 2012-05-06
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
#< #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
Thread-Index: AQHJimG5SNz22HBX3Em3WVMXPxzlJw==
Message-ID: <DE683DA100EC7649A8539A131020FF0F15E60D8CF8@fisd-mb02.ads.XYZisd.org>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
MIME-Version: 1.0
Watch Question

did you check whether the domain is blacklisted ...www.mxtoolbox.com.
Expert of the Quarter 2009
Expert of the Year 2009

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?

Confirmed that they are not blacklisted...
As for tracert, I will have the sender tracert to the addressee.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.