Exchange 2010 delaying/not sending/receiving emails from a single domain

ImImIn used Ask the Experts™
Exchange 2010 delaying/not sending/not receiving emails from a single domain.
As an example, after email sent get a delayed response back from exchange. Outlook header example:

MIME-Version: 1.0
From: Microsoft Outlook
To: <>
Date: Wed, 25 Mar 2015 20:57:51 -0400
Content-Type: multipart/report; report-type=delivery-status;
X-MS-Exchange-Organization-SCL: -1
Content-Language: en-US
Message-ID: <2ff0499a-28d9-454e-9b6b-763bfe243eea@EAGLESBSSERVER.EagleMachines.local>
In-Reply-To: <>
References: <000601d06735$39b3b2b0$ad1b1810$>
Thread-Topic: test
Thread-Index: AQHQZz3B7KyF7JcTnEaq5ZExk8rReZ0t8Ukf
Subject: Delivery delayed:Re: test
X-MS-Exchange-Organization-AuthSource: EAGLESBSSERVER.EagleMachines.local
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 05

Exchange General Info for the the same coming from Message Properties:

Identity: EAGLESBSSERVER\20656\29558
Subject: Re: test
Internet Message ID: <>
From Address:
Status: Ready
Size (KB): 15
Message Source Name: FromLocal
Source IP:
SCL: -1
Date Received: 3/25/2015 4:53:33 PM
Expiration Time: 3/27/2015 4:53:33 PM
Last Error: 400 4.4.7 Message delayed

Exchange is on a standalone SBS 2011 server in a VM environment.

Thank you for your help!

Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Looking at an SMTP log would help.  If you don't have logging turned on on your server (it's not on by default, IIRC), you can turn it on by editing the properties of your Send and Receive connector(s) and set it to Verbose logging on the General tab.  Then try sending another email to that address. After about 5-10 minutes, look at the SMTP log, searching it for the sending email addresses (i.e., and/or  Once you find the appropriate communications for the time frame when you sent the email, you can extract the needed information to a .txt file by finding all of the lines that refer to the same message ID.  Then we can take a look and see if there's any indication as to why the email didn't go through.

The log you would want to look at would be your SMTPSend log, which will be at the following location:

C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpSend

The first line of the message communication will look something like this:

2015-03-27T16:03:28.687Z,[Send Connector Name],08D224FB3E3146B8,0,,,*,,attempting to connect

The long number after the connector name is the message ID, 08D224FB3E3146B8 shown above, so you want to find all of the communication with that message ID number.


Thank you for your reply!
I did as you requested, sending a test email to the suspect email address but nothing concerning this send request was written to the SmtpSend log files!  I know this probably makes no sense? I searched by both and, received nothing for (or alleghencydimension). Searching for I found some files but nothing associated with OR EVEN THE TIME THE MESSAGE WAS SENT!


We are now getting 1 immediate "Undeliverable" message shortly after the message is sent and another 1 minute later!  Addresses are correct and nothing was written to either the SmtpSend or Receive logs.
I sent the last test from OWA and got the following information returned:

Undeliverable: TEST EMAIL from Schneider Computer Technologies on behalf of Eagle Machinery and Supply  
Microsoft Outlook  
Sent:  Tuesday, March 31, 2015 9:36 AM  
To:  sctuser
Delivery has failed to these recipients or groups: (
A problem occurred and this message couldn't be delivered. Check to be sure the e-mail address is correct. If the problem continues, please contact your helpdesk.

Diagnostic information for administrators:

Generating server: EAGLESBSSERVER.EagleMachines.local
#554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain ##

Original message headers:

Received: from EAGLESBSSERVER.EagleMachines.local
 ([fe80::417b:7c49:6758:43c4]) by EAGLESBSSERVER.EagleMachines.local
 ([fe80::417b:7c49:6758:43c4%10]) with mapi id 14.01.0438.000; Tue, 31 Mar
 2015 09:36:06 -0400
From: sctuser <>
To: "" <>
Subject: TEST EMAIL from Schneider Computer Technologies on behalf of Eagle
 Machinery and Supply
Thread-Topic: TEST EMAIL from Schneider Computer Technologies on behalf of
 Eagle Machinery and Supply
Thread-Index: AdBrt6GV4OrB7zsCQWiomOHnseXoCw==
Date: Tue, 31 Mar 2015 13:36:06 +0000
Message-ID: <C64A1FAF0CDBFD4C84298851BC4986F27CC8A084@EAGLESBSSERVER.EagleMachines.local>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Actually, it looks like that email address is mistyped.  The domain name is "" - you have an extra letter in there ""


Sorry about that, I will retry!


I resent my test email to: and the message was placed in the Messages queue in the Exchange Tools Queue Viewer with following details:


Identity: EAGLESBSSERVER\21083\31967
Subject: TEST EMAIL from Schneider Computer Technologies on behalf of Eagle Machinery and Supply  
Internet Message ID: <C64A1FAF0CDBFD4C84298851BC4986F27CC8B4B2@EAGLESBSSERVER.EagleMachines.local>
From Address:
Status: Ready
Size (KB): 2
Message Source Name: FromLocal
Source IP:
SCL: -1
Date Received: 3/31/2015 11:12:10 AM
Expiration Time: 4/2/2015 11:12:10 AM
Last Error:

After 20+ minutes, the message was still in the queue and not showing up in the SmtpSend log. I will wait for the message to empty from the Messages Queue and recheck the log at that time and update you with the results.  The message may take several hours or possibly even a day to empty to empty.

If you have anything else you want me to try, please advise.
Look in the message queue viewer, Queues tab, and find the "Last Error" column.  Often this will give you a clue as to why the message delivery has been delayed.


Nothing is listed there, Message Counts are all '0' and no data in the 'Last Error' column. Still have message sent hanging in the Messages queue though.
That sounds kind of weird. Can you take a screen capture of your Queues tab and Messages tab and post it here?


OK - I see the problem.  If you look at the bottom of the Queues tab, you'll see that it says "Items 3 to 4 of 4."  This is a little tricky thing that happens sometimes when you open the Queue viewer.  You have 2 other items in the queues tab that aren't showing.  Click the |< icon at the bottom to make sure you're viewing all of the items and then take another look/screen shot.
OK - looks like you're on a block list at Godaddy.  So, you need to submit an unblock request as shown in the message.  Do you have an SPF record and a PTR record for your domain?  If not, that might be why you got on the block list to start with.


WOW! I will look into this, not sure how I missed that? Thank you for your help. I will keep you posted.


Thank you, that fixed it and I learned a few things!


hypercat did a GREAT job helping me resolve this Exchange server issue. He stuck with me all along the way.  He does GREAT work!

Thank you hypercat!
Hey, Gary - thanks for the points and the praise. Glad to be of help.


Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial