Exchange Server - NDR a jejich význam

 

Exchange 2013    Exchange 2010    Exchange 2007    Exchange 2003

 

2013

List of Exchange 2013 NDR Codes and their Meanings

Temporary delivery failures

Enhanced status code Description Possible causes and solutions
4.3.1 Insufficient system resources Free disk space is low (for example, the disk that holds the queue database doesn't have the required amount of free space). For more information, see Understanding back pressure. To move the queue database to different disk, see Change the location of the queue database.
Available memory is low (for example, Exchange installed on a virtual machine that's configured to use dynamic memory). Always use static memory on Exchange virtual machines. For more information, see Exchange memory requirements and recommendations.
4.3.2 Service not available
or
Service not active
You've configured a custom Receive connector in the Transport (Hub) service on a Mailbox server that listens on port 25. Typically, custom Receive connectors that listen on port 25 belong in the Front End Transport service on the Mailbox server.
Important Exchange server components are inactive. You can confirm this by running the following command in the Exchange Management Shell: Get-ServerComponent -Identity <ServerName>.
To restart all inactive components, run the following command: Set-ServerComponentState -Identity <ServerName> -Component ServerWideOffline -State Active -Requester Maintenance.
Incompatible transport agents (in particular, after an Exchange update). After you identify the transport agent, disable it or uninstall it. For more information, see Troubleshoot transport agents.
4.4.1 Connection timed out Transient network issues that might eventually correct themselves. The Exchange server periodically tries to connect to the destination server to deliver the message. After multiple failures, the message is returned to the sender in an NDR with a permanent failure code.
For more information about configuring the queue retry and failure intervals, see Configure message retry, resubmit, and expiration intervals.
To manually retry a queue, see Retry queues.
Firewall or Internet service provider (ISP) restrictions on TCP port 25.
4.4.2 Connection dropped Transient network issues or server problems that might eventually correct themselves. The sending server will retry delivery of the message, and will generate further status reports.
The message size limit for the connection has been reached, or the message submission rate for the source IP address has exceeded the configured limit. For more information, see Message rate limits and throttling.
Antispam, SMTP proxy, or firewall configuration issues are blocking email from the Exchange server.
4.4.7 Message delayed
or
Queue expired; Message expired
Send connector configuration issues. For example:
• The Send connector is configured to use DNS routing when it should be using smart host routing, or vice-versa. Use nslookup to verify that the destination domain is reachable from the Exchange server.
• The FQDN that the Send connector provides to HELO or EHLO requests doesn't match the host name in your MX record (for example, mail.contoso.com). Some messaging systems are configured to compare these value in an effort to reduce spam. The default value on a Send connector is blank, which means the FQDN of the Exchange server is used (for example, exchange01.contoso.com).
The Mailbox Transport Delivery service isn't started on the destination server (which prevents the delivery of the message to the mailbox).
The destination messaging system has issues with Transport Neutral Encryption Format (TNEF) messages (also known as rich text format or RTF in Outlook). For example, meeting requests or messages with images embedded in the message body.
If the destination domain uses the Sender Policy Framework (SPF) to check message sources, there may be SPF issues with your domain (for example, your SPF record doesn't include all email sources for your domain).

Permanent delivery failures

Enhanced status code Description Possible causes and solutions.
5.1.0 Sender denied Replying to old messages, or messages that were exported as files (important recipient attributes might have changed). Verify that the recipient's email address is correct.
Malformed or missing attributes in contact entries.
The sender is blocked by sender filtering (directly, or the sender is on a user's Blocked Senders list, and the Sender Filter agent is configured to use safelist aggregation. For more information, see Sender filtering and Safelist aggregation.
5.1.1 RESOLVER.ADR.ExRecipNotFound; not found
or
User unknown
The recipient's email address is incorrect (the recipient doesn't exist in the destination messaging system). Verify the recipient's email address.
You recreated a deleted mailbox, and internal users are addressing email messages in Outlook or Outlook on the web using old entries in their autocomplete cache (the X.500 values or LegacyExchangeDN values for the recipient are now different). Tell users to delete the entry from their autocomplete cache and select the recipient again.
5.1.3 STOREDRV.Submit; invalid recipient address The recipient's email address is incorrect (for example, it contains unsupported characters or invalid formatting).
5.1.4 Recipient address reserved by RFC 2606 Receive connectors reject SMTP connections that contain the top level domains defined in RFC 2606 (.test, .example, .invalid, or .localhost), This behavior is controlled by the RejectReservedTopLevelRecipientDomains parameter on the New-ReceiveConnector and Set-ReceiveConnector cmdlets.
5.1.5 Recipient address reserved by RFC 2606 Receive connectors reject SMTP connections that contain the second level domains defined in RFC 2606 (example.com, example.net, or example.org). This behavior is controlled by the RejectReservedSecondLevelRecipientDomains parameter on the New-ReceiveConnector and Set-ReceiveConnector cmdlets.
5.1.6 Recipient addresses in single label domains not accepted Receive connectors reject SMTP connections that contain single label domains (for example, chris@contoso instead of chris@contoso.com) This behavior is controlled by the RejectSingleLabelRecipientDomains parameter on the New-ReceiveConnector and Set-ReceiveConnector cmdlets.
5.1.7 Invalid address
or
Unknown sender address
There's a problem with the sender's email address. Verify the sender's email address.
5.1.8 Access denied, bad outbound sender The sender has exceeded a message rate limit (for example, an application server is configured to relay a large number of messages through Exchange. For more information, see Message rate limits and throttling and Allow anonymous relay on Exchange servers.
5.2.1 Content Filter agent quarantined this message The message was quarantined by content filtering. To configure exceptions to content filtering, see Use the Exchange Management Shell to configure recipient and sender exceptions for content filtering.
5.2.2 Mailbox full The recipient's mailbox has exceeded its storage quota and is no longer able to accept new messages. For more information about configuring mailbox quotas, see Configure storage quotas for a mailbox.
5.2.3 RESOLVER.RST.RecipSizeLimit; message too large for this recipient The message is too large. Send the message again without any attachments, or configure a larger message size limit for the recipient. For more information, see Recipient limits.
5.3.0 Too many related errors The message was determined to be malformed, and was moved to the poison message queue. For more information, see Types of queues.
5.3.2 STOREDRV.Deliver: Missing or bad StoreDriver MDB properties You're using the ABP Routing agent, and the recipient isn't a member of the global address list that's specified in their address book policy (ABP). For more information, see Install and Configure the Address Book Policy Routing Agent and Address book policies in Exchange Server.
5.3.3 Unrecognized command Receive connectors that are used for internal mail flow are missing the required Exchange Server authentication mechanism. For more information about authentication on Receive connectors, see Receive connector authentication mechanisms.
5.3.4 Message size exceeds fixed maximum message size The message is too large. This error can be generated by the source or destination messaging system. Send the message again without any attachments, or configure a larger message size limit. For more information, see Message size limits in Exchange Server.
5.3.5 System incorrectly configured A mail loop was detected. Verify that the FQDN property on the Receive connector doesn't match the FQDN of another server, service, or device that's used in mail flow in your organization (by default, the Receive connector uses the FQDN of the Exchange server).
5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain There's a DNS or network adapter configuration issue on the Exchange server.
• Verify the internal and external DNS lookup settings for the Exchange by running these commands in the Exchange Management Shell:
Get-TransportService | Format-List Name,ExternalDNS*,InternalDNS*
Get-FrontEndTransportService | Format-List Name,ExternalDNS*,InternalDNS*
You can configure these settings by using the InternalDNS* and ExternalDNS* parameters on the Get-TransportService and Get-FrontEndTransportService cmdlets.
By default, these settings are used by Send connectors (the default value of the UseExternalDNSServersEnabled parameter value is $false).
• Check the priority (order) of the network adapters in the operating system of the Exchange server.
5.4.6 Hop count exceeded - possible mail loop A configuration error has caused an email loop. By default, after 20 iterations of an email loop, Exchange interrupts the loop and generates an NDR.
Verify that Inbox rules for the recipient and sender, or forwarding rules on the recipient 's mailbox aren't causing this (the message generates a message, which generates another message, and the process continues indefinitely).
Verify the mailbox doesn't have a targetAddress property value in Active Directory (this property corresponds to the ExternalEmailAddress parameter for mail users in Exchange).
If you remove Exchange servers, or modify settings related to mail routing an mail flow, be sure to restart the Microsoft Exchange Transport and Exchange Frontend Transport services.
5.5.2 Send hello first SMTP commands are sent out of sequence (for example, a server sends an SMTP command like AUTH or MAIL FROM before identifying itself with the EHLO command). After establishing a connection to a messaging server, the first SMTP command must always be EHLO or HELO.
5.5.3 Too many recipients The combined total of recipients on the To, Cc, and Bcc lines of the message exceeds the total number of recipients allowed in a single message for the organization, Receive connector, or sender. For more information, see Message size limits in Exchange Server.
5.7.1 Unable to relay
or
Client was not authenticated
You have an application server or device that's trying to relay messages through Exchange. For more information, see Allow anonymous relay on Exchange servers.
The recipient is configured to only accept messages from authenticated (typically, internal) senders. For more information, see Configure message delivery restrictions for a mailbox.
5.7.3 Cannot achieve Exchange Server authentication
or
Not Authorized
A firewall or other device is blocking the Extended SMTP command that's required for Exchange Server authentication (X-EXPS).
Internal email traffic is flowing through connectors that aren't configured to use the Exchange Server authentication method . Verify the remote IP address ranges on any custom Receive connectors.
5.7.900
to
5.7.999
Delivery not authorized, message refused The message was rejected by a mail flow rule (also known as a transport rule). This enhanced status code range is available when the rule is configured to reject messages (otherwise, the default code that's used is 5.7.1). For more information, see Mail flow rule actions in Exchange Server.

 

 

2010

List of Exchange 2010 NDR Codes and their Meanings

NDR
Code

Explanation of Enhanced Status Codes in Exchange 2010 NDRs
4.2.2 The recipient has exceeded their mailbox limit. 
Alternatively it could mean that the delivery directory on the Virtual server has exceeded its limit.
4.3.1 Insufficient system resources.  This normally translates to not enough disk space on the delivery server. 
Microsoft say this Exchange NDR may be reported as out-of-memory error.
4.3.2 A classic temporary problem.  Most probably, the Exchange Administrator has frozen the queue.
4.4.1 Intermittent network connection.  The server has not yet responded.  A classic time-out problem.  If it persists, you will also get a 5.4.x status code error.
4.4.2 The server started to deliver the message but then the connection was dropped.  The sending server will retry automatically.
4.4.6 Too many hops.  Most likely, the message is looping.
4.4.7 Problem with a protocol timeout, for example a message header limit.  Check your receiving server connectors.
4.4.9 A DNS problem.  Check your smart host setting on the SMTP connector.  For example, check correct SMTP format. Also, use square brackets in the IP address [198.81.23.4]  You can get this non-delivery error if you have been deleting routing groups.
4.6.5 Multi-language situation.  Your server does not have the correct language code page installed.
5.0.0 SMTP 500 reply code means an unrecognised address.  You get this NDR when you make a typing mistake, such as trying to send email via telnet.
The most likely cause is a routing error.  Another solution maybe to add an * in the address space.
A separate cause for NDR 5.0.0 is a DNS problem.

5.1.x Exchange 2010 NDR problems with email address.
5.1.0 Sender denied.  NDR often seen with contacts. Verify the recipient address.
Also Mismatched Network Card duplex setting.
5.1.1 Bad destination mailbox address.  5.1.1 is the most common Exchange 2010 NDR; there is a problem with the recipient address. 
Perhaps the recipient does not exist. 
Possibly the user was moved to another server in Active Directory. 
Check for mailbox delegation.
Maybe an Outlook client replied to a message while offline.
Check the Exchange connector configuration.
5.1.2 SMTP; 550 Host unknown.  An error is triggered when the host name can’t be found.  For example, when trying to send an email to bill@ nowheredomain.com.
[Example kindly sent in by Paul T.]
N.B.
You can create custom DSN (Delivery Status Notification) messages for senders using PowerShell’s New-SystemMessage.
5.1.3 Invalid recipient address.  Another problem often seen with contacts.  Address field may be empty.  Check the address information.  Or there could be a syntax error.
5.1.4 Destination mailbox address ambiguous. Two objects have the same address, which confuses the Exchange 2010 Categorizer.
5.1.5 Destination mailbox address invalid.
5.1.6 Problem with homeMDB or msExchHomeServerName – check how many users are affected.  Sometimes running RUS (Recipient Update Service) cures this problem.  Mailbox may have moved.
5.1.7 Invalid address. Problem with senders mail attribute, check properties sheet in ADUC.
5.1.8 Something the matter with sender’s address
5.2.x NDR caused by the size of the email.
5.2.1 Mailbox cannot be accessed.  Perhaps the message is too large.  Alternatively, the mailbox has been disabled, or is offline. Check the recipient’s mailbox.
Else it could be a permissions problem, particularly on a Public Folder.  If so, try this PowerShell Command:
get-PublicFolderClientPermission "\ProblemFolder"
5.2.2 Sadly, the recipient has exceeded their mailbox storage quota.
5.2.3 Recipient cannot receive messages this big.  The server or connector limit exceeded.  Try resending the message without the attachment.
5.2.4 Most likely, a distribution list or group is trying to send an email.  Check where the expansion server is situated.  The application event log may have an Event ID 6025 or 6026, which has more detailed information.
5.3.0 Problem with MTA, maybe someone has been editing the registry to disable the MTA / Store driver.
5.3.1 Mail system full.  Disk full problem on the mailbox server?
5.3.2 System not accepting network messages.  Look outside Exchange for a connectivity problem.
5.3.3 Remote server has insufficient disk space to hold email.  Check SMTP log.  This error often happens when the sending server is using an ESMTP BDAT command.
5.3.4 Message too big.  Check the limits on both the sender and receiver side.  There may be a policy in operation.
5.3.5 System incorrectly configured.  Multiple Virtual Servers are using the same IP address and port. See Microsoft TechNet article: 321721 Sharing SMTP.  Email probably looping.
5.4.0 DNS Problem.  Check the Smart host, or check your DNS. It means that there is no DNS server that can resolve this email address.  Could be Virtual Server SMTP address.
5.4.1 No answer from host.  Not Exchange’s fault check connections.
5.4.2 Bad connection.
5.4.3 Routing server failure.  No available route.
5.4.4 Cannot find the next hop, check the Routing Group Connector.  Perhaps you have Exchange servers in different Routing Groups, but no connector.  Configuring an MX record may help.
5.4.6 Tricky looping problem, a contact has the same email address as an Active Directory user. 
One user is probably using an Alternate Recipient with the same email address as a contact.
Check recipient policy.
5.4.7 Delivery time-out.  Message is taking too long to be delivered.
5.4.8 Microsoft advise, check your recipient policy. SMTP address should be yourdom.com. 
NOT server.yourdom.com.
5.5.0 Underlying SMTP 500 error.  Our server tried ehlo, the recipient’s server did not understand and returned a 550 or 500 error.  Set up SMTP logging.
5.5.1 Invalid command.  (Rare Exchange NDR)
5.5.2 Possibly the disk holding the operating system is full.  Alternatively, it could be a syntax error if you are executing SMTP from telnet.
5.5.3 Too many recipients.  More than 5,000 recipients.  Check the Global Settings, Message Delivery properties.  Try resending the same message to fewer recipients.
5.5.4 Invalid domain name.  The true cause may be an invalid character.
5.5.5 Wrong protocol version.
5.5.6 Invalid message content.  This is a protocol error, thus you should get more information by looking in the application log.
5.6.0 Corrupt message content.  Try sending without attachment.
5.6.1 Media not supported.
5.6.3 More than 250 attachments.
5.7.1 A very common Exchange 2010 NDR, the cause is a permissions problem.  For some reason the sender is not allowed to email this account. 
Perhaps an anonymous user is trying to send mail to a distribution list.
Alternatively, a user may have a manually created email address that does not match a System Policy.

Check SMTP Virtual Server Access Tab.  Try checking this box: Allow computers which successfully authenticate to relay. 
Check the outgoing SMTP logs.
Check: Mailbox – <Mailboxname> – Properties – Mail Flow Settings – Message delivery restrictions.
Try disabling Windows-Integrated-Security.  Instead allow only standard authorization on the SMTP receiver on the Exchange 2010 server.
Check Attachment filtering on the Edge server.
5.7.2 Distribution list cannot expand and so is unable to deliver its messages.
5.7.3 Not Authorized, security problem.  It could be that the sender cannot send to the alternative address.  
On another tack, check external IP address of ISA server. Make sure it matches the SMTP publishing rule.
5.7.4 Extra security features not supported.  Check delivery server settings
5.7.5 Cryptographic failure.  Try a plain message with encryption.
5.7.6 Certificate problem, encryption level may be to high.
5.7.7 Message integrity problem.
  See more on Exchange Non-delivery Reports.

 

 

 

2007

List of Exchange 2007 NDR Codes and their Meanings

NDR
Code

Explanation of Enhanced Status Codes in Exchange 2007 NDRs
4.2.2 The recipient has exceeded their mailbox limit. 
It could also be that the delivery directory on the Virtual server has exceeded its limit.
4.3.1 Insufficient system resources.  This normally means not enough disk space on the delivery server. 
Microsoft say this Exchange NDR maybe reported as out-of-memory error.
4.3.2 A classic temporary problem.  Most likely, the Administrator has frozen the queue.
4.4.1 Intermittent network connection.  The server has not yet responded.  Classic time-out problem.  If it persists, you will also get a 5.4.x status code error.
4.4.2 The server started to deliver the message but then the connection was dropped.  The sending server is configured to retry automatically.
4.4.6 Too many hops.  Most likely, the message is looping.
4.4.7 Problem with a protocol timeout, for example a message header limit.  Check receiving server connectors.
4.4.9 A DNS problem.  Check your smart host setting on the SMTP connector.  For example, check correct SMTP format. Also, use square brackets in the IP address [197.89.1.4]  You can get this same NDR error if you have been deleting routing groups.
4.6.5 Multi-language situation.  Your server does not have the correct language code page installed.
5.0.0 SMTP 500 reply code means an unrecognised address.  You get this NDR when you make a typing mistake when you manually try to send email via telnet.
The most likely cause is a routing error.  One solution maybe to add an * in the address space.
A separate cause for NDR 5.0.0 is a DNS problem.
 
5.1.x Exchange 2007 NDR problems with email address.
5.1.0 Sender denied.  Often seen with contacts. Verify the recipient address.
Mismatched Network Card duplex setting.
5.1.1 Bad destination mailbox address.  5.1.1 is the most common Exchange 2007 NDR; there is a problem with the recipient address. 
Maybe the recipient does not exist. 
Possibly the user was moved to another server in Active Directory. 
Check mailbox delegation.
Maybe an Outlook client replied to a message while offline.
Check connector configuration.
5.1.2 SMTP; 550 Host unknown.  An error is triggered when the host name can’t be found.  For example, when trying to send an email to bob@ nonexistantdomain.com.
[Example kindly sent in by Paul T.]
5.1.3 Invalid recipient address.  Another problem often seen with contacts.  Address field maybe empty.  Check the address information.  Or there could be a syntax error.
5.1.4 Destination mailbox address ambiguous. Two objects have the same address, which confuses the Exchange 2007 Categorizer.
5.1.5 Destination mailbox address invalid.
5.1.6 Problem with homeMDB or msExchHomeServerName – check how many users are affected.  Sometimes running RUS (Recipient Update Service) cures this problem.  Mailbox may have moved.
5.1.7 Invalid address. Problem with senders mail attribute, check properties sheet in ADUC.
5.1.8 Something the matter with sender’s address
5.2.x NDR caused by the large size of the email.
5.2.1 Mailbox cannot be accessed.  Perhaps the message is too large.  Alternatively, the mailbox has been disabled, or is offline. Check the recipient’s mailbox.
Else it could be a permissions problem, particularly on a Public Folder.  If so, try this PowerShell Command:
get-PublicFolderClientPermission "\ProblemFolder"
5.2.2 Sadly, the recipient has exceeded their mailbox storage quota.
5.2.3 Recipient cannot receive messages this big.  The server or connector limit exceeded.  Try resending the message without the attachment.
5.2.4 Most likely, a distribution list or group is trying to send an email.  Check where the expansion server is situated.  The application event log may have an Event ID 6025 or 6026, which has more detailed information.
5.3.0 Problem with MTA, maybe someone has been editing the registry to disable the MTA / Store driver.
5.3.1 Mail system full.  Disk full problem on the mailbox server?
5.3.2 System not accepting network messages.  Look outside Exchange for a connectivity problem.
5.3.3 Remote server has insufficient disk space to hold email.  Check SMTP log.  This error often happens when the sending server is using an ESMTP BDAT command.
5.3.4 Message too big.  Check the limits on both the sender and receiver side.  There maybe a policy in operation.
5.3.5 System incorrectly configured.  Multiple Virtual Servers are using the same IP address and port. See Microsoft TechNet article: 321721 Sharing SMTP.  Email probably looping.
5.4.0 DNS Problem.  Check the Smart host, or check your DNS. It means that there is no DNS server that can resolve this email address.  Could be Virtual Server SMTP address.
5.4.1 No answer from host.  Not Exchange’s fault check connections.
5.4.2 Bad connection.
5.4.3 Routing server failure.  No available route.
5.4.4 Cannot find the next hop, check the Routing Group Connector.  Perhaps you have Exchange servers in different Routing Groups, but no connector.  Configuring an MX record may help.
5.4.6 Tricky looping problem, a contact has the same email address as an Active Directory user. 
One user is probably using an Alternate Recipient with the same email address as a contact.
Check recipient policy.
5.4.7 Delivery time-out.  Message is taking too long to be delivered.
5.4.8 Microsoft advise, check your recipient policy. SMTP address should be yourdom.com. 
NOT server.yourdom.com.
5.5.0 Underlying SMTP 500 error.  Our server tried ehlo, the recipient’s server did not understand and returned a 550 or 500 error.  Set up SMTP logging.
5.5.1 Invalid command.  (Rare Exchange NDR)
5.5.2 Possibly the disk holding the operating system is full.  Alternatively, it could be a syntax error if you are executing SMTP from telnet.
5.5.3 Too many recipients.  More than 5,000 recipients.  Check the Global Settings, Message Delivery properties.  Try resending the same message to fewer recipients.
5.5.4 Invalid domain name.  The true cause maybe an invalid character.

5.5.5 Wrong protocol version.
5.5.6 Invalid message content.  This is a protocol error, thus you should get more information by looking in the application log.
5.6.0 Corrupt message content.  Try sending without attachment.
5.6.1 Media not supported.
5.6.3 More than 250 attachments.
5.7.1 A very common Exchange 2007 NDR, the cause is a permissions problem.  For some reason the sender is not allowed to email this account. 
Perhaps an anonymous user is trying to send mail to a distribution list. 
Alternatively, a user may have a manually created email address that does not match a System Policy.

Check SMTP Virtual Server Access Tab.  Try checking this box: Allow computers which successfully authenticate to relay. 
Check the outgoing SMTP logs.
Check: Mailbox – <Mailboxname> – Properties – Mail Flow Settings – Message delivery restrictions.
Try disabling Windows-Integrated-Security.  Instead allow only standard authorization on the SMTP receiver on the Exchange 2007 server.
Check Attachment filtering on the Edge server.
5.7.2 Distribution list cannot expand and so is unable to deliver its messages.
5.7.3 Not Authorized, security problem.  It could be that the sender cannot send to the alternative address.  
On another tack, check external IP address of ISA server. Make sure it matches the SMTP publishing rule.
5.7.4 Extra security features not supported.  Check delivery server settings
5.7.5 Cryptographic failure.  Try a plain message with encryption.
5.7.6 Certificate problem, encryption level maybe to high.
5.7.7 Message integrity problem.

 

 

2003

List of Exchange 2003 NDR Codes and their Meanings

NDR
Code

Explanation of Non-Delivery Report error codes for Exchange Server
(See here for Exchange 2007 NDR codes)
4.2.2 The recipient has exceeded their mailbox limit.  It could also be that the delivery directory on the Virtual server has exceeded its limit. (Default 22 MB)
4.3.1 Not enough disk space on the delivery server.  Microsoft say this NDR maybe reported as out-of-memory error.
4.3.2 Classic temporary problem, the Administrator has frozen the queue.
4.4.1 Intermittent network connection.  The server has not yet responded.  Classic temporary problem.  If it persists, you will also a 5.4.x status code error.
4.4.2 The server started to deliver the message but then the connection was broken.
4.4.6 Too many hops.  Most likely, the message is looping.
4.4.7 Problem with a timeout.  Check receiving server connectors.
4.4.9 A DNS problem.  Check your smart host setting on the SMTP connector.  For example, check correct SMTP format. Also, use square brackets in the IP address [197.89.1.4]  You can get this same NDR error if you have been deleting routing groups.
4.6.5 Multi-language situation.  Your server does not have the correct language code page installed.
5.0.0 SMTP 500 reply code means an unrecognised command.  You get this NDR when you make a typing mistake when you manually try to send email via telnet.
More likely, a routing group error, no routing connector, or no suitable address space in the connector.  (Try adding * in the address space)
This status code is a general error message in Exchange 2000.  In fact Microsoft introduced a service pack to make sure now get a more specific code.

5.1.x Problem with email address.
5.1.0 Often seen with contacts. Check the recipient address.
5.1.1 Another problem with the recipient address.  Possibly the user was moved to another server in Active Directory.  Maybe an Outlook client replied to a message while offline.
5.1.2 SMTP; 550 Host unknown.  An error is triggered when the host name can’t be found.  For example, when trying to send an email to bob@ nonexistantdomain.com.
[Example kindly sent in by Paul T.]
5.1.3 Another problem with contacts.  Address field maybe empty.  Check the address information.
5.1.4 Two objects have the same address, which confuses the categorizer.
5.1.5 Destination mailbox address invalid.
5.1.6 Problem with homeMDB or msExchHomeServerName – check how many users are affected.  Sometimes running RUS (Recipient Update Service) cures this problem.  Mailbox may have moved.
5.1.7 Problem with senders mail attribute, check properties sheet in ADUC.
5.2.x NDR caused by a problem with the large size of the email.
5.2.1 The message is too large.  Else it could be a permissions problem.  Check the recipient’s mailbox.
5.2.2 Sadly, the recipient has exceeded their mailbox limit.
5.2.3 Recipient cannot receive messages this big.  Server or connector limit exceeded.
5.2.4 Most likely, a distribution list or group is trying to send an email.  Check where the expansion server is situated.
5.3.0 Problem with MTA, maybe someone has been editing the registry to disable the MTA / Store driver.
5.3.1 Mail system full.  Possibly a Standard edition of Exchange reached the 16 GB limit.
5.3.2 System not accepting network messages.  Look outside Exchange for a connectivity problem.
5.3.3 Remote server has insufficient disk space to hold email.  Check SMTP log.
5.3.4 Message too big.  Check limits, System Policy, connector, virtual server.
5.3.5 Multiple Virtual Servers are using the same IP address and port. See Microsoft TechNet article: 321721 Sharing SMTP.  Email probably looping.
5.4.0 DNS Problem.  Check the Smart host, or check your DNS. It means that there is no DNS server that can resolve this email address.  Could be Virtual Server SMTP address.
5.4.1 No answer from host.  Not Exchange’s fault check connections.
5.4.2 Bad connection.
5.4.3 Routing server failure.  No available route.
5.4.4 Cannot find the next hop, check the Routing Group Connector.  Perhaps you have Exchange servers in different Routing Groups, but no connector.
5.4.6 Tricky looping problem, a contact has the same email address as an Active Directory user.  One user is probably using an Alternate Recipient with the same email address as a contact.
5.4.7 Delivery time-out.  Message is taking too long to be delivered.
5.4.8 Microsoft advise, check your recipient policy. SMTP address should be cp.com. 
NOT server.cp.com.
5.5.0 Underlying SMTP 500 error.  Our server tried ehlo, the recipient’s server did not understand and returned a 550 or 500 error.  Set up SMTP logging.
5.5.2 Possibly the disk holding the operating system is full.  Or could be a syntax error if you are executing SMTP from a telnet shell.
5.5.3 More than 5,000 recipients.  Check the Global Settings, Message Delivery properties.
5.5.5 Wrong protocol version
5.6.3 More than 250 attachments.
5.7.1 Permissions problem.  For some reason the sender is not allowed to email this account.  Perhaps an anonymous user is trying to send mail to a distribution list.
Check SMTP Virtual Server Access Tab.  Try checking this box: Allow computers which successfully authenticate to relay
User may have a manually created email address that does not match a System Policy.
5.7.2 Distribution list cannot expand and so is unable to deliver its messages.
5.7.3 Check external IP address of ISA server. Make sure it matches the SMTP publishing rule.
5.7.4 Extra security features not supported.  Check delivery server settings
5.7.5 Cryptographic failure.  Try a plain message with encryption.
5.7.6 Certificate problem, encryption level maybe to high.
5.7.7 Message integrity problem.