Opens in a new tab

SMTP 552: exceeded storage allocation — what it means

552 means the message exceeds a size limit — the server’s, or the recipient’s mailbox. It is permanent: the same message will be refused again. The one exception is an old use for too many recipients, which senders treat as the temporary 452.

Code552
MeaningRequested mail action aborted: exceeded storage allocation
KindPermanent failure — the sender gives up
Sent in reply toMAIL (a declared size too big), RCPT and the end of the message
What the sender doesReturns the message to the sender
Defined inRFC 5321, section 4.2; RFC 1870

Paste your bounce

Paste the line with the code — or the whole bounce: we explain each code in it, say whether the sender will try again, and link the service’s own page where it has one. It is read in your browser; nothing is sent.

What causes it

  • The message, with its attachments, is larger than the server accepts.
  • The recipient’s mailbox is full and inactive.
  • Headers too large — some servers limit their size and number.

What to do

  • Send the file by link rather than attachment, or make it smaller — attachments grow by about a third when encoded.
  • For a full mailbox: reach the recipient another way.

What each provider means by it

WhoWhat they say
Gmail552 5.3.4 for a message over its size limit, too many attachments or headers too large; 552 5.2.2 for an inbox out of storage and inactive; 552 5.7.0 for a blocked file type.
Exchange Server5.3.4 for a message over the size limit; 5.2.3 for one too large for this recipient.
PostfixRefuses messages over message_size_limit — 10,240,000 bytes by default.
EximFails incoming messages over its message_size_limit with 552.

Worth knowing

A server that advertises SIZE and accepted the declared size should not refuse the message for size afterwards, unless it turned out larger (RFC 1870).

In Exchange Online, 5.2.2 means the sender exceeded a sending quota — not a full mailbox.

Related: 5.3.4, 5.2.2, 452, 5.2.3.

Sources

Checked on 27 September 2026 against these official sources:

See every bounce before your customers do

Add your domain and send us a test message: we show what a receiving server saw — authentication, reverse DNS, blocklists, TLS — and monitor the servers you send from for blocklistings every day. Free for your first domain.

Create a free account