Generic SMTP

552 5.3.4 Message too large — reduce the email size

552 5.3.4

The message was larger than a mail system could accept. The limit may belong to your outbound service, the recipient's gateway, the destination mailbox provider, or an intermediate security system. Attachments expand during email encoding, so a file below a published limit can still produce a message above it.

How to fix it

  1. 1

    Remove or compress attachments

    Delete unnecessary files, compress suitable documents, and resize large images. Remember that email encoding adds overhead beyond the original file size.

  2. 2

    Share large files with a controlled link

    Put the file in an approved storage service and send an access-controlled link instead of attaching it.

  3. 3

    Check both sides' limits

    Compare the sending service, outbound gateway, recipient gateway, and mailbox-provider limits. The smallest enforced limit wins.

  4. 4

    Resend only after the message changes

    This is a 5-class permanent result for the oversized message. Queue retries of the same bytes will not make it fit.

Meaning current as of 2026-07-15, cross-checked against the provider's own documentation. Providers do occasionally redefine codes — if this doesn't match what you're seeing, the source link is the authoritative reference.

Common questions

Why did a 20 MB attachment exceed a 25 MB limit?+

Base64 and MIME packaging increase the transmitted message size, commonly by roughly one third before other headers and body parts are counted.

Is 552 5.3.4 a recipient mailbox quota error?+

Not normally. 5.3.4 is message too big for the system; mailbox quota is commonly represented by a 2.2 detail code.

Should the server retry this bounce?+

Not unchanged. Reduce the message below the effective limit or replace attachments with links first.