Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1391
  • Last Modified:

MSExchangeTransport Event ID:3008 A NDR with status code 5.0.0

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;derek@mallardgroup.net (Message-ID  <1224687996.5656@minpost.nu>).  
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>
0
BrettAMair
Asked:
BrettAMair
  • 5
  • 3
3 Solutions
 
Scott1201Commented:
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?
0
 
BrettAMairAuthor Commented:
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.
0
 
flyingskyCommented:
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.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
BrettAMairAuthor Commented:
NO, we were having too many issues with reverse DNS lookup so we turned that off months ago.
0
 
BrettAMairAuthor Commented:
I ran the Exchange Troubleshooter and this happens...

Cannot identify an object with 'dena.stanely@mallardgroup.net' 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.
0
 
Scott1201Commented:
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 @mallardgroup.net 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...)
0
 
BrettAMairAuthor Commented:
Scott, I checked that earlier as well. All is good in that aspect.
0
 
Scott1201Commented:
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 beyondlogic.org, 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.
0
 
BrettAMairAuthor Commented:
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.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now