Exchange 2003 Not Delivering Internal Messages
Exchange Server 2003. Windows Server 2003. I am having recurring instances where people within our domain are not able to send messages to other people within our domain (<user>@goodnewsjail.org sending to <user2>@goodnewsjail.org). We have a spam filter (IMF Tune). But I understand that IMF Tune only filters emails coming in from outside our domain. When one of our internal users sends to another internal user, they get the following message from Exchange: 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. <mail.goodnewsjail.org #5.2.1> This does not happen to everyone or all the time, just to a few users and intermittently. However, it is happening enough to gum up things for a few. What might be the issue? Any help will be appreciated. Thanks.Dr. Douglas Pruiett Good News Jail & Prison Ministry Richmond, Virginia www.goodnewsjail.org
February 28th, 2011 10:14am

Good explanation of codes here: http://www.computerperformance.co.uk/exchange2003/exchange2003_NDR.htm 5.2.1 may mean that the message will make the mailbox exceed its allowed limit. Or something like that.Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m
Free Windows Admin Tool Kit Click here and download it now
February 28th, 2011 10:24am

On the page I linked, the suggestion for 5.2.1 is "The message is too large. Else it could be a permissions problem. Check the recipient's mailbox."Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m
February 28th, 2011 10:26am

The messages being rejected have no attachments and consist of a small text message. So it is not a message too large. I am not sure what permissions would cause the problem. In one instance the error occurs when the user is sending to me. But they are eventually able to send a message through to me letting me know about their error on a previous message.Dr. Douglas Pruiett Good News Jail & Prison Ministry Richmond, Virginia www.goodnewsjail.org
Free Windows Admin Tool Kit Click here and download it now
February 28th, 2011 10:50am

How about a telnet test from one user to the other? telnet servername 25 mail from: user1@domain.com rcpt to: user2@domain.com data hello there . Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m
February 28th, 2011 11:16am

I tried the telnet test, and each time I get the following: 550 5.7.1 Requested action not taken. Message refused. This happens no matter the from and to accounts. I tried sending from me to me and got the same error. However, I have no problem sedning from me to me in Outlook through Exchange on the same server. Any ideas?Dr. Douglas Pruiett Good News Jail & Prison Ministry Richmond, Virginia www.goodnewsjail.org
Free Windows Admin Tool Kit Click here and download it now
February 28th, 2011 1:08pm

Do you have just one Exchange Server or many? Are all patched and up to date? Can you give a little more descrition on what your environment looks like. I found this rather matching (except for it being for Public Folders) - You receive a "5.2.1" non-delivery report when you send an e-mail message to a public folder on Exchange Server 2003 or on Exchange 2000 Server Anything in that article that rings a bell?Jesper Bernle | Blog: http://xchangeserver.wordpress.com
February 28th, 2011 1:41pm

Jesper: I have a single Exchange Server 2003, patched and up to date. The Exchange Server runs on a Windows 2003 Server. I just looked in the event log under applications and find the following recurring events (errors). Is there any connection with my issue? Event ID 9667 on MSExchangeIS: Failed to create a new named property for database "First Storage Group\Mailbox Store (GNSERVER)" because the number of named properties reached the quota limit (8192). User attempting to create the named property: "phil.vangorp" Named property GUID: 00020386-0000-0000-c000-000000000046 Named property name/id: "x-add_date" The named property varies. Dr. Douglas Pruiett Good News Jail & Prison Ministry Richmond, Virginia www.goodnewsjail.org
Free Windows Admin Tool Kit Click here and download it now
February 28th, 2011 1:51pm

It sounds like what has become a fairly well-known problem in previous versions of Exchange. You need to increase that quota limit. I think this describes what you need to do. http://www.netomatix.com/Articles/KBArticle.aspx?a=820379Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m
February 28th, 2011 1:59pm

The article indicates that the quota limit is a protection against attacks on the system. The article says the default (without making any registry changes) is 16,000. Yet my system reports 8,192. Also, in the registry I find the following key with value 8,192 under each public and private DB key: NonMAPI Named Props Quota I am a little uneasy about adding keys as indicated by the article. Moreover, is this issue related to the initial post regarding non-delivered messages?Dr. Douglas Pruiett Good News Jail & Prison Ministry Richmond, Virginia www.goodnewsjail.org
Free Windows Admin Tool Kit Click here and download it now
February 28th, 2011 2:16pm

Yes, the limit will originally have been in place for a good reason. But it seems that all kinds of processes think it's a good idea to add message headers these days, and they've proliferated somewhat. It's odd that the article says that the default value for the max number of entries is 16000, but that the default value for the reg key is 8192, and I've no explanation for that. I think this could certainly be relevant to the initial post. A search reveals more information that might interest you: http://www.google.com/#sclient=psy&q=%22the+number+of+named+properties+reached+the+quota+limit+(8192)%22 Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m
February 28th, 2011 3:49pm

Ahh, okay. Well, as Lee said, this isn't all that uncommon. Please refer to: Confused About Named Properties Quotas in Exchange 2003 and Exchange 2007? Join the Club!Jesper Bernle | Blog: http://xchangeserver.wordpress.com
Free Windows Admin Tool Kit Click here and download it now
March 1st, 2011 4:23am

Hi, As Lee mentioned, Named Properties consists of both “Named Props Quota” and “NonMAPI Named Props Quota”. So, to resolve the Event ID 9667 issue, please add both the “Named Props Quota” and “NonMAPI Named Props Quota” registry values to the registry key. Alternatively, you can move the mailbox to a new store. Thanks. NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
March 2nd, 2011 9:32pm

Novak: 1. To what value do you suggest I set these quotas? They are apparently at 8192 now. 2. How do I move a mailbox to a new store (and how do I create a new store)? Thanks for the help.Dr. Douglas Pruiett Good News Jail & Prison Ministry Richmond, Virginia www.goodnewsjail.org
Free Windows Admin Tool Kit Click here and download it now
March 3rd, 2011 8:56am

No reason not to use the maximum values. From the article linked above: Value name: Named Props Quota Value type: REG_DWORD Value data: positive integer between 1 and 0x7FFF Value name: Replids Quota Value type: REG_DWORD Value data: positive integer between 1 and 0x7FFF Value name: NonMAPI Named Props Quota Value type: REG_DWORD Value data: positive integer between 1 and 0x7FFF 0x7FFF is 32767 if you're entering them in decimal. I'd worry about moving the mailbox only if this doesn't work.Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m
March 3rd, 2011 9:15am

Okay. I changed the NonMAPI key to 32767 and added a Named Props Quota key, set to 32767. I will see if this licks the problem and will report. Thanks.Dr. Douglas Pruiett Good News Jail & Prison Ministry Richmond, Virginia www.goodnewsjail.org
Free Windows Admin Tool Kit Click here and download it now
March 3rd, 2011 11:34am

Please try Lee’s suggestion to check the result. If there is any update, please feel free to let us know. Regards, NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
March 3rd, 2011 8:45pm

Hi all I have the issue where some internal users cannot email public folders. They get NDR #5.2.1 as per the initial post. Just wanted to know if this solved the problem for anyone meaning the last post from Lee
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2012 8:40am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics