Geeks With Blogs
Hornet's Nest A few of Mike Hoerner's Favorite Topics


In an Exchange 2003 environment that has matured over time, an enabled Active Directory account may get a #5.2.1 Undeliverable message (NDR) as shown below when they send an e-mail message to another enabled Active Directory account.

From: System Administrator
Sent: March 30, 2009 9:30 AM
To: Bob Stevens
Subject: Let's meet at Noon

Your message did not reach some or all of the intended recipients.

     Subject: Let's meet at Noon
     Sent: 3/30/2009 9:30 AM

The following recipient(s) cannot be reached:

     Smith, Billy on 3/30/2009 9:30 AM
     The message reached the recipient's e-mail system, but delivery
was refused. Attempt to resend the message. If it still fails, contact
     your system administrator.  <serverName.FQDN #5.2.1>


To troubleshoot and resolve the issue, you will need to do three things:

1)  Document where the recipient mailbox resides (Exchange Server name, Storage Group, and Mailbox Store)

2)  Log on the Exchange 2003 Server where the recipient mailbox resides and review the Application Event log for a 9667 Error event.  Verify the Storage Group and Mailbox Store for the recipient mailbox is listed in the Description field. 
For example, if the recipient mailbox resides in First Storage Group | Mailbox Store 3, then the following 9667 event will have that listed in the Description field as shown below.

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9667
Date: 3/30/2009
Time: 9:32 AM
User: N/A
Computer: Exchange Server name
Description: Failed to create a new named property for database
"First Storage Group\Mailbox Store 3" because the number of named
properties reached the quota limit (8192). User attempted to create
the named property: "outlookapp"
Named property GUID: 00010375-0000-0000-b000-000000000055
Named property name/id: "X-W-MSG"


3) To resolve the issue, you will need modify and increase the quota for the named property in the registry for the Mailbox Store the recipient mailbox resides on.  Also, I recommend that you increase the quota for the non-MAPI name property for the same Mailbox Store as well.

For more information how to modify the registry for the named properties (Named Props Quota) and non-MAPI name properties (NonMAPI Named Props Quota) registry DWORD values, check out  Please note the TechNet article refers to Exchange 2007 Databases.  The information in the article also applies to Exchange 2003 databases.

Please note the default quota is 8192 and I recommend increasing it to at least 16,384 (the maximum limit is 32767). 


If you need to identify the Object GUID for an Exchange 2003 Mailbox Store, for more information, please refer to

In addition, there are two other ways to resolve a #5.2.1 Undeliverable message (NDR) for a recipient mailbox.  You can move the recipient mailbox to another mailbox store that does not have any 9667 events listed in the Application Event log or you can move all user mailboxes from the Mailbox Store to different mailbox store, delete the empty mailbox store, create a new Mailbox Store, and move the users back.

More Information

In a nutshell, the primary reason for the #5.2.1 Undeliverable message (NDR) above has to do with Named Properties and X-Headers.  Jason Nelson published an article: Name Properties, X-Headers, and You on The Microsoft Exchange Team Blog regarding this topic.  For more information, check it out.

Posted on Tuesday, June 9, 2009 2:00 PM | Back to top

Comments on this post: Another reason for a #5.2.1 Undeliverable message (NDR)

# re: Another reason for a #5.2.1 Undeliverable message (NDR)
Requesting Gravatar...
One of the most important articles if your doing a transition from Exchange 2003 to 2010.

Hats off to you my friend.

The following issue can be resolved by the "above mentioned" technet article
just reposted it here for ease of use
Left by DIFFMEISTER on Jun 20, 2010 3:45 AM

Your comment:
 (will show your gravatar)

Copyright © BWCA | Powered by: