XADM: PR_MESSAGE_FLAGS MSGFLAG_UNMODIFIED Bit Not Set CorrectlyLast reviewed: February 27, 1998Article ID: Q181871 |
The information in this article applies to:
- Microsoft Exchange Server, version 5.5
SYMPTOMSA MAPI transport provider explicitly sets the MSGFLAG_UNMODIFIED bit for the PR_MESSAGE_FLAGS property of a new message during the call to the IXPLOGON::StartMessage() method, and the bit is not set on the message when delivery is set to the Exchange Server information store. If default delivery is changed to a personal folder (PST) file, the new message will have the MSGFLAG_UNMODIFIED bit set.
CAUSEThe Exchange Server information store was explicitly setting the MSGFLAG_UNMODIFIED bit for the PR_MESSAGE_FLAGS property only in the case where the information store delivered the message. When a transport provider is "receiving" new messages, messages are essentially created in the Inbox, not delivered.
WORKAROUNDTo work around this problem, set default delivery for the messaging client to a personal folder.
STATUSMicrosoft has confirmed this to be a problem in Exchange Server version 5.5. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information. Keywords : XADM kbusage Version : 5.5 Platform : WINDOWS Issue type : kbbug Solution Type : kbpending |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |