This article was previously published under Q188631
This article has been archived. It is offered "as is" and will no longer be updated.
The creation, modification, and deletion of messages in public folders thathave many thousands of messages may appear slow.
The Exchange Server information store maintains data for every clientregarding the read or unread status of every message. This per-userread/unread processing can cause operations to appear slow when the numberof messages in the public folder is very large.
To work around this problem, create a hierarchy of folders to distributethe messages so that fewer messages are in each folder.
Microsoft recognizes the need for disabling per-user read/unread processingfor specific folders in certain circumstances. We have modified MicrosoftExchange Server 5.5 so that it is possible to programmatically disable thisprocessing on a particular folder.
To obtain this feature, obtain the latest service pack for Exchange Serverversion 5.5. For more information, please see the following article in theMicrosoft Knowledge Base:
191014XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
The English version of this feature should have the following fileattributes or later:
File Name Version ----------------------- STORE.EXE 5.5.2435.0 MDBMSG.DLL 5.5.2435.0 GAPI32.DLL 5.5.2435.0
This feature was first included in Exchange Server 5.5 Service Pack 2.
Disabling per-user read/unread processing for a folder causes the stateof read/unread properties to become inconsistent for objects in the folder.This inconsistency may cause confusion among users who expect that they caninfluence the read/unread state of a message.
To disable per-user read/unread processing for a public folder, a newMAPI folder property has been created. The new property has the followingdefinition and will eventually be added to the EDKMDB.H header fileincluded in the Microsoft Platform SDK. Until such time, you must add theproperty definition manually in your source code.