X.3.4 · Mail system
SMTP enhanced status code 5.3.4
Message too big for system
X.3.4 means the message is bigger than the receiving system's per-message size limit. It is permanent for that message, and the same message will fail every time.
| Registry code | X.3.4 |
|---|---|
| Forms in use | 5.3.4 |
| Registry name | Message too big for system |
| Subject | 3: Mail system |
| Permanent or temporary | 5.x.x permanent failure: resending unchanged will not succeed |
| Associated basic codes | 552, 554 |
| Defined in | [RFC 3463] |
What the registry says
The message is larger than per-message size limit. This limit may either be for physical or administrative reasons. This is useful only as a permanent error.
IANA SMTP Enhanced Status Codes registry, X.3.4
The basic codes it travels with
- 552 Requested mail action aborted: exceeded storage allocation
- 554 Transaction failed (Or, in the case of a connection-opening response, "No SMTP service here")
In practice
Size limits vary by server: Gmail names its message, attachment and header limits in the reply text, and other servers set their own caps. Attachments grow by about a third when base64-encoded, so a file under the limit on disk can exceed it in the message. A message that fails with 5.3.4 will fail every time, so shrink it or send a link.
What the sender should do
Remove large attachments and share them as links, or compress them, then resend.
Would verifying the list have prevented 5.3.4?
No
This reply is about your sending setup, the message or the receiving system, not about whether the address exists, so verifying the list will not prevent it.
How providers use X.3.4
Quoted from each provider’s own error reference.
- Gmail 552 5.3.4
Your message exceeded Google's message size limits. To view our message size guidelines, go to Send attachments with your Gmail message.
Common questions
- What does 5.3.4 mean?
- X.3.4 means the message is bigger than the receiving system's per-message size limit. It is permanent for that message, and the same message will fail every time.
- What should I do about 5.3.4?
- Remove large attachments and share them as links, or compress them, then resend.
- Would an email verifier have caught 5.3.4?
- No. This reply is about your sending setup, the message or the receiving system, not about whether the address exists, so verifying the list will not prevent it.
Full guides for this code
Sources
- IANA: SMTP Enhanced Status Codes registry (checked 2026-11-05)
- RFC 3463: Enhanced Mail System Status Codes (checked 2026-11-05)
- RFC 5321: Simple Mail Transfer Protocol, section 4.2.3 (reply codes) (checked 2026-11-05)
- Google Workspace Admin Help: Gmail SMTP errors and codes (checked 2026-11-05)
Registry and provider wording is quoted exactly; guidance is written by the SimpleVerifier Team.
SimpleVerifier Team · Last checked against the sources 2026-11-05