Forward or Reply may Fail on a message with an attachment from a 3rd Party MAPI/CDO client in Exchange 2010

When a mailbox is on Exchange 2010 and the� global MaxSendSize and MaxReciveSize� size limits in your organization or on the mailbox are over 409mb, when you attempt to reply or forward a message with an attachment from a 3rd party application that uses the client MAPI/CDO binaries you receive a red �X� on the device and the message cannot be sent.

In addition the following error will be logged for the 3rd party application service account in the RPC Client Access logs on the CAS server role-

2010-08-24T16:44:15.193Z,22987,4,/o=Test Org/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=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

The above will occur regardless of attachment size.

Outlook/OWApp are unaffected by this issue.

Due to how the RpcClientAccess resource tracker component computes memory allocation size if the maximum send/receive limit is over 409mb a negative number will be returned resulting in message submission failure.

This only affects some 3rd party applications that call the client MAPI/CDO binaries.

This issue will be fixed in Exchange 2010 sp1 RU2.

Workaround:

As a workaround it is recommended to lower the MAxSendSize and MaxReceiveSize values to a value less than 409mb.

The MaxSendSize and MaxReceiveSize values can be set in two places.

Globally this can be set using the Set-TransportConfig�� -MaxSendSize <Value> -MaxReceiveSize <Value> parameters.

This value can also be set on a mailbox specifically with Set-Mailbox �Identity <Alias>�� -MaxSendSize <Value> -MaxReceiveSize <Value>

Ensure that both the global and local values are below 409mb.

One example of a symptom of this issue is a person attempting to reply to a a message with an attachment from their Smart Phone will receive a red �x� on the device.�

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.