Answer
A user has attempted to send a message that has exceeded the maximum message size that is allowed to be sent outbound from the server. GMS has deleted the message and sent a notification to the user with the following contents:Failed mail: exceeded maximum outgoing message size.
If the client had implemented the Enhanced SMTP SIZE command, the attempt to send the message would have been rejected at the protocol stage instead of being transmitted to the server in its entireity first (and therefore wasting a considerable amount of bandwidth). GMS saves resources by carrying out this check once per email message (and not for each recipient of the email message).
This mail message has exceeded the maximum outgoing message size.
In this case, session Undefined was receiveing a message from the client at Undefined apparently from Undefined. The message was rejected with
Undefined
The message was Undefined bytes in length and the maximum size is Undefined.
To resolve this issue, change the maximum outgoing message size in the user’s profile. Remember that attachments are encoded when appended to messages and increase in size by about 30%. For example, an attachment of 10MB will result in an email message about 13MB in size.
To reduce the waste of bandwidth caused by this failure, contact the manufacturer of the mail client and ask them to implement the ESMTP SIZE command.
See Also:
- What is the SMTP MAIL clause?
- How do I contact the owner of a client?
- How do I contact the owner of a remote server?
- What is SMTP Response Code Theory?
Keywords:size too big outgoing MaxMessageSizeOut