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.
This only affects some 3rd party applications that call the client MAPI/CDO binaries.
As a workaround it is recommended to lower the MAxSendSize and MaxReceiveSize values to a value less than 409mb.
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.
Article ID: 2447520 - Last Review: Oct 18, 2010 - Revision: 1