XADM: PR_MESSAGE_FLAGS MSGFLAG_UNMODIFIED Bit Not Set Correctly

Last reviewed: February 27, 1998
Article ID: Q181871
The information in this article applies to:

- Microsoft Exchange Server, version 5.5

SYMPTOMS

A 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.

CAUSE

The 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.

WORKAROUND

To work around this problem, set default delivery for the messaging client to a personal folder.

STATUS

Microsoft 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


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 27, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.