Assume that a mailbox is located on an Exchange 2010 server, and that the global MaxSendSize and MaxReceiveSize attributes for the organization or the mailbox are larger than 409MB. In this situation, third party clients that use the MAPI/CDO libraries (for example, Blackberry) will be unable to forward or reply to messages containing attachments. Additionally, the following error will be logged in the RPC Client Access log:
2010-08-24T16:44:15.193Z,22987,4,/o=Test Org/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Blackberry Administrator,,,6.0.8153.0,Classic,,,ncacn_ip_tcp,,0,,,RopHandler: OpenStream: Attempted to use more memory than allowed. Reserve memory request = 272.. Error code = MaxSubmissionExceeded2010-08-24T16:44:15.193Z,22987,4,/o=Test Org/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Blackberry Administrator,,,6.0.8153.0,Classic,,,ncacn_ip_tcp,,0,,,RopHandler: OpenStream: Attempted to use more memory than allowed. Reserve memory request = 272.. Error code = MaxSubmissionExceeded
To resolve this issue, install the following update rollup:
2425179 Description of Update Rollup 2 for Exchange Server 2010 Service Pack 1
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The information and the solution in this document represents the current view of Microsoft Corporation on these issues as of the date of publication. This solution is available through Microsoft or through a third-party provider. Microsoft does not specifically recommend any third-party provider or third-party solution that this article might describe. There might also be other third-party providers or third-party solutions that this article does not describe. Because Microsoft must respond to changing market conditions, this information should not be interpreted to be a commitment by Microsoft. Microsoft cannot guarantee or endorse the accuracy of any information or of any solution that is presented by Microsoft or by any mentioned third-party provider.
Microsoft makes no warranties and excludes all representations, warranties, and conditions whether express, implied, or statutory. These include but are not limited to representations, warranties, or conditions of title, non-infringement, satisfactory condition, merchantability, and fitness for a particular purpose, with regard to any service, solution, product, or any other materials or information. In no event will Microsoft be liable for any third-party solution that this article mentions.
To work around this issue, ensure that the global Send/Receive size limits for the organization and for the mailbox are under 409mb.