Hello, on Exchange 2010 what is the best way to troubleshoot why a message has been returned back. Example message did not reach some or all of the intended recipients. Thanks

On Wed, 9 Feb 2011 16:16:58 +0000, acmsoft wrote: >on Exchange 2010 what is the best way to troubleshoot why a message has been returned back. > >Example message did not reach some or all of the intended recipients. Message tracking would show you the FAIL event. But the NDR should have the reason for the failure in it, too. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hello, this is the error I have to why it came back undelivered 0x80004005-00000000-00000000

NDR is a good way to go. If emails are flowing in/out of youhr organization, you could use dnsstuff to query the recepient.

On Fri, 11 Feb 2011 15:47:49 +0000, acmsoft wrote: >this is the error I have to why it came back undelivered > >0x80004005-00000000-00000000 Can you post the entire NDR? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi acmsoft, Please paste the entire NDR in your next post, this is an important information to help us troubleshoot the issue. Besides that, I suggest you follow these steps to troubleshoot the problem: 1. Use Exbpa to do a health check for the Exchange Server. 2. Check the event log. If there is any error please paste in your next post. Here is a post about error 0x80004005-00000000-00000000, hope it can give you some help: users suddenly started getting when they try to send out a email to internal or external users "This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80004005-00000000-00000000]" http://social.technet.microsoft.com/Forums/en/exchangesvrgeneral/thread/08c4350f-7bad-47b6-94a4-a85b50776785 Thanks, EvanPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Unfortunately that was the only error I got however it was a temporary issue as all is working fine thanks