552 error: Exceeded storage allocation or message too large
Either the recipient's mailbox is full or the message is larger than the server allows.
How to fix 552
- Shrink or remove attachments; if the mailbox is full, retry later.
Why this happens
The recipient's mailbox itself can't take the message right now - it is full, disabled or temporarily unavailable. It has nothing to do with your content or reputation.
How to keep it from coming back
You can't prevent a recipient's full mailbox, but you can avoid sending repeatedly to addresses that keep returning it, and remove them if the error persists across several attempts.
Should I retry a 552 error?
Not as it stands. A permanent error means the same message will be refused again until the cause is fixed on your side. Fix the cause first, then send a fresh message; if it keeps failing after that, check the full text of the bounce for the exact reason.
Got the full bounce message?
The text after the code names the exact reason, and the same code can mean different things at different receivers. Paste the whole message into the decoder - it runs in your browser and nothing is sent.
Open the bounce decoderRelated error codes
Seeing this again and again? That's usually a reputation or authentication problem we can trace and fix at the source.
How we help: Consulting · Private infrastructure · Managed mailboxes · Monthly support