4.2.3 Email Bounce Error
Reason
Message Is Too Long: Delayed Message
The email message has not yet been delivered because it was longer than the recipient’s email address’s email system allows.
How to fix?
Try to divide the text and/or attachments into two or more separate emails. Check that the message contained only the intended text and attachments. Some systems count attachments as part of the message length.
4.2.3 – Official definition from ITEF
For the code that starts from 4.X.X
A persistent transient failure is one in which the message as sent is valid, but persistence of some temporary condition has caused abandonment or delay of attempts to send the message. If this code accompanies a delivery failure report, sending in the future may be successful.
For the code that starts from X.2.3
A per-mailbox administrative message length limit has been exceeded. This status code should be used when the per-mailbox message length limit is less than the general system limit. This code should be used as a permanent failure.
5.2.3 Email Bounce Error
Reason
Message Is Too Long: Message Not Delivered
The message could not be delivered because it was longer than the recipient’s email system allows.
How to fix?
Try to divide the text and/or attachments into two or more separate emails. Check that the message contained only the intended text and attachments. Some systems count attachments as part of the message length.
5.2.3 – Official definition from ITEF
For the code that starts from 5.X.X
A permanent failure is one which is not likely to be resolved by resending the message in the current form. Some change to the message or the destination must be made for successful delivery.
For the code that starts from X.2.3
A per-mailbox administrative message length limit has been exceeded. This status code should be used when the per-mailbox message length limit is less than the general system limit. This code should be used as a permanent failure.
