MSExchangeTransport Event ID:3008 A NDR with status code 5.0.0

Posted on 2008-10-22
Last Modified: 2012-05-05
This is the error I'm receiving when an external client tries to send us mail...

A non-delivery report with a status code of 5.0.0 was generated for recipient rfc822; (Message-ID  <>).  
Cause:  This indicates a permanent failure. Possible causes :  1)No route is defined for a given address space. For example, an SMTP connector is configured, but this recipient address does not match the address spaces for which it routes mail.  2)Domain Name Server (DNS) returned an authoritative host not found for the domain.  3)The routing group does not have a connector defined û mail from one server in the routing group has no way to get to another routing group.    
Solution: Verify that this error is not caused by a DNS lookup problem, and then check the address spaces configured on your STMP connectors. If you are delivering Internet mail through an SMTP connector,  consider adding an address space of type SMTP with value ô*ö (an asterisk) to one of the SMTP connectors to make routing possible. Verify all routing groups are connected to each other through a routing group connector or another connector.

Here is what the NDR says that the external clients receive...
Your message did not reach some or all of the intended recipients.
The email system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator. #5.0.0>
Question by:BrettAMair
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3

Expert Comment

ID: 22778045
Can you provide some background on your network configuration?  Is there one Exchange server, are you setting up a new domain from scratch or has this server worked for inbound email in the past?  Are you converting from a different email server application?

Author Comment

ID: 22778103
It's the only server in the domain. Mail was working fine. Ran updates, stopped working. I reran service pack 2 for Exchange, still getting the same errors. Nothing is being converted.
LVL 18

Assisted Solution

flyingsky earned 100 total points
ID: 22778116
are you doing reserse lookup of IP to fight SPAM? Looks like the IP address this email coming from cannot be resolved to the correct name by your Exchange/Anti-spam.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.


Author Comment

ID: 22778144
NO, we were having too many issues with reverse DNS lookup so we turned that off months ago.

Author Comment

ID: 22778209
I ran the Exchange Troubleshooter and this happens...

Cannot identify an object with '' as the mail address in Active Directory. Please check if this address is correct and rerun the tool.

When I go to ESM>Recipients>All GLobal Adress LIsts> and preview, it shows my users and their correct addresses.

Expert Comment

ID: 22778391
If you check the properties of a user account in AD Users and Computers from the Exchange server, do you see the correct e-mail address on the E-Mail Addresses tab?  If you go to ESM - Recipients - Recipient Policies, open the Properties for the Default Policy (and any other Policies on the server).  Make sure that the domain is listed on the E-Mail Addresses tab.  Click the Edit button, the check box should be selected (Exchange Server... responsible for all mail delivery...)

Author Comment

ID: 22778424
Scott, I checked that earlier as well. All is good in that aspect.

Assisted Solution

Scott1201 earned 100 total points
ID: 22778481
Brett, can you obtain a simple SMTP client program and try to send an SMTP message from an internal PC to a user on your network?  I've used BMail, from, frequently.  Documentation is pretty basic, you should be able to specify To, From, Server, and a brief message body.  Might also be worthwhile to see what happens if you try to send a message through your server to an outside host - relay blocking could keep this from working, in which case you may need to authenticate to your server.

I'd also suggest turning up the SMTP logging in ESM, which may give us more information about the errors.

Accepted Solution

BrettAMair earned 0 total points
ID: 22780258
Ok, I uninstalled and reinstalled IIS. I then reinstalled Exchange and reran service pack 2. It works now. Somehow my IIS database became corrupt when I uninstalled Symantec Endpoint.

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
how to add IIS SMTP to handle application/Scanner relays into office 365.

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question