Unable to receive email from 1 company/domain

We have one company trying to send us email, and they are getting an error message (Remote server returned #5.2.1 - problem with recipients mailbox)

This is an SBS 03 Server w/Exchange 03. I checked the App logs on the server, and its showing this codes:

9667 - Failed to create a new named property for database "First Storage Group\Mailbox Store " because the number of named properties reached the quota limit (8192).
 User attempting to create the named property: "SYSTEM"
 Named property GUID: 00020386-0000-0000-c000-000000000046
 Named property name/id: "x-forefront-prvs"

7515 - An error occurred while Microsoft Exchange Intelligent Message Filter attempted to filter a message with ID  <ddf27b72e5b74286b78e2179edeaff13@BN1PR05MB360.namprd05.prod.outlook.com>, P1 From smtp:mmoran@dsi-group.com and Subject  RE:  email issue. This message will not be filtered. The error code is 0x800710f0.
LVL 4
Cobra25Asked:
Who is Participating?
 
Leon KammerCommented:
Hi,

To give you an idea of what's happening,  when mail arrives, it can contain any number of customer “X-“ headers and their associated values.

When the message is converted to MAPI format, the X- headers are saved inside the EDB file which has a maximum quota store of 32K, but is generally left at the default of 8K, each unique X- header encountered becomes a separate entry in the named props table.

You have 3 options to fix this:
1)
Run MFCMapi and then open your mailbox and run “Property Pane”/”Find All Named Props”.
Find which application (spam software, archiving, Disclaimer) uses most of the property quota and delete them.
The idea behind dumping is to look at the props and figure out what program they are for and fix it.

2)
Create 2 new mailbox stores on the server.
Move 50 % of mailboxes from the database to the new mailbox store and the remaining ones to the second one.
After moving the mailboxes, ensure you run the cleanup agent.

3)
Change the Registry value of NonMAPI Named Props Quota from 8192 (default) to 16384 in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\Server Name\Private
Then unmount and remount the store.

Cheers

Leon
0
 
Cobra25Author Commented:
Leon, thanks!

I plan on trying #3.

Is there a risk by changing this key value?
0
 
Leon KammerCommented:
Hi,

The value has a maximum of 32K...
Best practice states that you should not exceed 16K as a soft limit because if you hit the hard limit, the store basically becomes inoperable.

If you choose to increase the store size, just make certain that you keep an eye on the number of entries and remove those which are no longer required, as increasing this to 32K and forgetting about it could be disasterous.

Cheers

Leon
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Cobra25Author Commented:
Thanks -

How do i know how many entries are in use and how to remove them?
0
 
Leon KammerCommented:
Hi,

This link will give you an idea on how to monitor the number of entries in the store.http://support.microsoft.com/kb/254606

Also this link will give you an idea how best to tackle the issue.
http://blogs.technet.com/b/exchange/archive/2010/07/29/3410545.aspx
http://technet.microsoft.com/en-us/library/bb851495%28EXCHG.80%29.aspx

Cheers

Leon
0
 
Cobra25Author Commented:
Thanks Leon your solution did the trick.
0
 
Leon KammerCommented:
You are very welcome :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.