5.2.3 SMTP bounce: message too large

What 5.2.3 means

The message is larger than the recipient mailbox's administrative size limit. Permanent for this message.

Message text

Message length exceeds administrative limit

Common causes of 5.2.3

• Message with large attachments exceeds the per-mailbox limit

How to fix 5.2.3

1. Reduce message size: remove or compress attachments, or send a link.
2. Do not resend the same message unchanged.

Check your domain

Read the headers of a bounced messageRuns in your browser; nothing is uploaded.

Have the full bounce message? Paste it into the bounce code lookup and it will match the code and the provider for you. Open the bounce code lookup.

How to read 5.2.3

The second part, 5.2.3, is an enhanced status code (RFC 3463 §2) written class.subject.detail. Class 5 is a Permanent failure (5xx): the command was rejected and the sender should not repeat it unchanged (RFC 5321 §4.2.1; RFC 3463 §2).. Subject 2 is mailbox: a problem with the recipient mailbox, such as full, disabled or unknown. The detail number refines the subject, and providers may define details of their own, which is why one code can read differently at Gmail, Microsoft and Yahoo.

Do not keep resending the same message: a permanent failure repeats until the cause is fixed. Correct the cause, then send a new message.

Official source: www.rfc-editor.org. Last verified 2026-10-20.

Related guides

• How to create an SPF record (syntax and examples)
• How DKIM works and how to publish a DKIM record
• How to set up a DMARC record, from p=none to p=reject

Related codes

• 5.2.2 SMTP: mailbox full
• 550 SMTP: mailbox unavailable
• 551 SMTP: user not local
• 552 SMTP: storage exceeded
• 553 SMTP: mailbox name not allowed
• 554 SMTP: transaction failed

FAQ

All bounce codes