# 552 5.3.4: message too big for system

URL: https://iblockspam.com/smtp-errors/552-5-3-4
Last updated: 2026-10-09

Code: 552 5.3.4 (permanent failure, the message bounced)
Provider: Standard (RFC)

Your message is larger than the receiving system's per-message limit. Attachments are the usual cause, and resending the same message will fail again.

What the bounce says:

```
552 5.3.4 Your message exceeded Google's message size limits.
```
Start of Gmail's text, as listed in Google's SMTP errors reference.

RFC 3463 defines X.3.4 as "Message too big for system": the message is larger than the per-message size limit, which may be physical or administrative. It is useful only as a permanent error.

Gmail uses 552 5.3.4 for several limits: overall message size, the number of attachments, total header size, and the size of a single header such as Subject. The text says which limit you hit.

Size limits apply to the encoded message, not the files on your disk. Email usually carries attachments in Base64 (RFC 2045), which turns every 3 bytes into 4 characters, so a message grows by about a third on the way. Each server along the path can also have its own limit, including the one that sends on your behalf, so the smallest limit wins. A server can also advertise its limit up front with the SIZE extension; the bounce may come from your own server if it saw that limit.

## Common causes

- Attachments push the encoded message over the receiver's limit.
- Too many attachments for the receiver.
- Very large headers, often from automated systems or long recipient lists.

## How to fix it (sender)

- Share large files through a link to cloud storage instead of attaching them.
- Compress or split attachments into several messages.
- For automated mail, check what is inflating the headers.

## How to fix it (recipient or admin)

- If partners regularly need to send large files, agree on a file-sharing service or raise your own limit where your provider allows.

**Q: My attachment is under the limit. Why did it bounce?**
Encoding makes it larger: Base64 adds about a third. Other parts of the message and every server on the path count too, and the smallest limit along the way applies.

**Q: How do I send a file that is too large for email?**
Upload it to a file-sharing or cloud storage service and email a link. That also avoids filling the recipient's mailbox.

Sources:
- RFC 3463: Enhanced Mail System Status Codes: https://www.rfc-editor.org/rfc/rfc3463
- Gmail SMTP errors and codes (Google Workspace Admin Help): https://knowledge.workspace.google.com/admin/support/troubleshooting/gmail-smtp-errors-and-codes
- RFC 2045: MIME part one, section 6.8 (Base64 encoding): https://www.rfc-editor.org/rfc/rfc2045#section-6.8

---

Source: iBlockSpam, https://iblockspam.com/smtp-errors/552-5-3-4 (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt