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 usingPowerShell'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

 Exchange 2010 | 更多分享链接

发表评论：

About Me

Archives Categories

Replies List

My FriendLinks

Blog Info