Consider the following scenario:
You configure a message size limit in a Microsoft Exchange Server 2010 environment.
A user receives an email message whose original size is less than the size limit. However, the size of the message exceeds the size limit after a content conversion. Or, after the user receives the message, you reduce the size limit to a size that is lower than the size of the existing email message.
You try to move the mailbox to a target mailbox database by running the New-MoveRequest cmdlet together with the BadItemLimit 0 parameter.
In this scenario, the move operation fails, and you receive one of the following error messages:
Error message 1
Error: The mailbox exceeded the maximum number of corrupted items that were specified for this move request.
Error message 2
Error: A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox
This issue occurs because the message size limit is enforced on the message item incorrectly during the move operation.
To resolve this issue, install the update rollup that is described in the following article in the Microsoft Knowledge Bases:
2685289 Description of Update Rollup 3 for Exchange Server 2010 Service Pack 2 After you apply this update rollup, you should run the New-MoveRequest cmdlet together with the AllowLargeItems parameter when you move the mailbox.
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 New-MoveRequest cmdlet, go to the following Microsoft website:
New-MoveRequestFor more information about message size limits, go to the following Microsoft website:
Understanding Message Size LimitsFor more information about how to troubleshoot mailbox moves, go to the following Microsoft website:
Troubleshooting Mailbox MovesFor more information about content conversion, go to the following Microsoft website: