Article ID: 979480 - View products that this article applies to.
Consider the following scenario:
Note This problem does not occur when users access the mailboxes that were moved by using Microsoft Office Outlook in MAPI mode or by using Microsoft Office Outlook Web Access (OWA).
This problem occurs because the Unique Identifier attributes of the messages change when the mailboxes are moved. However, the UIDNEXT attributes of the folders do not change when the mailboxes are moved. When IMAP4 clients try to synchronize the new messages, the UIDNEXT attribute should be referenced. However, no messages match the UIDNEXT attribute. This behavior occurs because the sequence of Unique Identifier attributes of the messages already changed.
To fix this problem, install the following update rollup:
(https://support.microsoft.com/kb/979611/ )Description of Update Rollup 2 for Exchange Server 2010: February 18, 2010
NoteOnce a mailbox has been moved to an Exchange Server 2010 server before the hotfix is installed, the Unique Identifier (UID) attributes on the messages is broken because the hotfix keeps the old UID attributes during the mailbox moving process. To fix the problem on the affected mailbox, you can use an Outlook client to move all the messages from the Inbox folder to a new mail folder and then move them back to the Inbox folder. This behavior will rewrite the UID attributes correctly and the new messages should start to work.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the Unique Identifier attribute and UIDNEXT attribute, visit the following IETF Web site:
General information about the Internet Message Access Protocol - Version 4rev1
Article ID: 979480 - Last Review: March 4, 2010 - Revision: 1.2