552: storage allocation exceeded
The receiving server aborted the message because it exceeded a storage limit, usually a full mailbox or a message larger than allowed.
- Standard
- Provider
- Permanent (5xx)
- Class
- Sources checked
- Author
At a glance
- Code
- 552
- Provider
- Standard SMTP codes
- Temporary or permanent
- PermanentRefused for good: the message comes back to the sender, and resending it gets the same answer.
- Who has to act
- Either side, depending on the cause. Start with the checks below that are yours.
- What the server says
552 Requested mail action aborted: exceeded storage allocation
What it means
RFC 5321 defines 552 as exceeded storage allocation. In practice it covers two cases: the recipient's mailbox is over quota (552 5.2.2), or the message is larger than the server or the mailbox accepts (552 5.3.4 or 5.2.3). RFC 5321 also notes that RFC 821 wrongly listed 552 for too many recipients and asks clients to treat a 552 in that situation as temporary. Otherwise it is permanent and the message is returned. The enhanced code tells you whether to wait for space or make the message smaller.
Common causes
- The recipient's mailbox is full (5.2.2).
- The message is larger than the server's or the mailbox's size limit (5.3.4, 5.2.3).
- Too many recipients, on older servers that still use 552 for it.
How to fix it
- 01Check the enhanced code: 5.2.2 means a full mailbox, 5.3.4 or 5.2.3 a message that is too big.
- 02For a full mailbox, tell the recipient and try again later.
- 03For size, remove or shrink attachments, or share files by link.
Sources
What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.
- RFC 5321, section 4.2.3: Reply Codes in Numeric Orderrfc-editor.org
- RFC 5321, section 4.5.3.1.10: Too Many Recipients Coderfc-editor.org
Related codes
- 5.2.2Mailbox full.The recipient's mailbox has reached its storage quota, so the server will not take more mail until the owner deletes messages or gets more space.
- 5.3.4Message too big.The message is larger than the maximum size the receiving system accepts for any message, so it was refused and has to be made smaller.
- 5.2.3Message too large for this mailbox.The message is bigger than the size limit set for this particular mailbox, which an administrator set lower than the system-wide limit.
- 452Insufficient system storage.The receiving server is short of storage or has hit a limit, such as the number of recipients in one message, and asks the sender to try again later.
552 at other providers
- 552Message too large.The message is larger than Xfinity accepts. Xfinity takes messages of 15 MB or smaller, so reduce the size and send it again.
- 552Recipient mailbox is full.The recipient's GMX mailbox has no room left, either in storage or in the number of emails it may hold, so the message was refused.
- 552Message too large.The message is larger than the recipient mailbox or the GMX server accepts, so it was refused. Make it smaller and send it again.
- 552Recipient mailbox is full.The recipient's IONOS mailbox has no free space left, so the message could not be delivered. Only the recipient can free space.
All 105 standard codesEvery code in the wikiPaste your own bounce