Users do not receive new messages if they use IMAP4 clients to access mailboxes that were moved to another Exchange Server 2010 RU1 server

Article translations Article translations
Article ID: 979480 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • You install Update Rollup 1 for Microsoft Exchange Server 2010 on computers that are running Exchange Server 2010.
  • You move mailboxes from one server to another server within the same database availability group.
  • Users use IMAP4 clients to access the mailboxes.
In this scenario, the users can view the old messages that were received before their mailboxes were moved. However, the users cannot view new messages.

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

CAUSE

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.

RESOLUTION

To fix this problem, install the following update rollup:
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.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION



For more information about the Unique Identifier attribute and UIDNEXT attribute, visit the following IETF Web site:

Properties

Article ID: 979480 - Last Review: March 4, 2010 - Revision: 1.2
APPLIES TO
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
Keywords: 
kbexpertiseinter kbsurveynew kbhotfixrollup kbfix kbqfe KB979480

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com