Answer
GMS is in the process of receiving a message from a remote mail server using Enhanced SMTP (ESMTP). ESMTP allows the receiving system to verify that the message is acceptable before the message is transferred. This process means that GMS can dramatically reduce the amount of bandwidth required using standard SMTP. The remote system wishes to send a message which is for a user that is not local to this server and the incoming message exceeds the maximum size of message that is allowed to be transmitted outbound from the server. GMS has therefore rejected the message. By rejecting the message at the MAIL clause, GMS is saving considerable network bandwidth because the message body has not been sent over the network.
In this case, session Undefined received a connection from the message server at Undefined to accept a message apparently from Undefined. The MAIL command was
Undefined
and GMS responded with
Undefined
. The message is Undefined bytes long which is greater than the maximum outgoing message that is allowed to be sent (Undefined bytes).
To resolve this issue you will need to increase the maximum outgoing message size that is allowed through the server. The maximum message size is set using the domain variable "MaxMessageSizeOut" and the message returned is held in the global variable "MaxMessageSizeOutMes".
The maximum allowed outbound message size can be controlled on a per domain basis from GMS Anti-Spam > Connect > Outbound Sizes page.
See Also:
- What is the SMTP MAIL clause?
- What is the maximum message size in #gms#?
- What is SMTP Response Code Theory?
- Why do I see SIZE errors in the SMTP log?
- Do you support quotas and message size limits?
Keywords:SIZE RFC1870 bandwidth resources MaxMessageSizeOut MaxMessageSizeOutMes user restriction control