// how to fix
Bounce "552 5.2.2": the mailbox is full
The recipient has run out of storage space. It is their problem, not yours, but repeated "mailbox full" bounces often mean an abandoned address.
What it means
Your email came back with a message such as:
552 5.2.2 The email account that you tried to reach is over quota
Other wordings include Mailbox full, Quota exceeded or Insufficient storage. Sometimes the code starts with 452 4.2.2 instead: that is the temporary version, and your server will keep trying for a while.
It means the recipient's mailbox has no space left. The address exists, but the server cannot store anything new until the person deletes some emails or buys more space.
Why it matters
- Your setup is not at fault: SPF, DKIM and DMARC have nothing to do with this error.
- The person will not see your email until they free up space.
- An address that stays full for weeks is usually abandoned. Nobody reads it, and some providers later turn old abandoned mailboxes into spam traps.
How to check
- Read the bounce: it names the full mailbox and the server that refused it.
- Look at its history: in your newsletter tool, check whether the same address bounced as "full" in earlier campaigns.
- Check large attachments: a very big attachment can be refused by a nearly full mailbox while small emails still get through.
How to fix it
- For one important contact: reach them another way (phone, another address) and tell them their mailbox is full. Once they clean it, resend your email.
- Send smaller emails: share large files with a download link instead of an attachment.
- For mailing lists: let your tool handle it. Most treat "mailbox full" as a soft bounce and retry on the next campaign.
- Remove addresses that stay full. If an address bounces as full on three or more campaigns in a row, or for more than a month, remove it or move it to an inactive segment.
- Do not resend in a loop. Sending the same email again and again to a full mailbox will not help and can look like spam.
If the full mailbox is yours
If people tell you their emails to your address bounce with 5.2.2, your own mailbox is full. Delete old emails with big attachments, empty the trash and spam folders, or upgrade your storage plan with your provider. With Google accounts, storage is shared with Google Drive and Photos, so large files there count too.
Check that it is fixed
For a contact: once they confirm they freed space, send one short email and check that no bounce comes back. For a list: watch your next campaign reports and make sure repeat "mailbox full" addresses are no longer being sent to.
Check that it is fixed
DNS changes can take from a few minutes to a few hours. Then send a new test email or scan your domain again.
Related guides
- Gmail bounce "550 5.7.26": unauthenticated emailGmail refused your email because it could not confirm it comes from your domain. SPF, DKIM or DMARC is missing or failing. Here is how to fix it.
- Bounce "550 5.7.1": message rejected or blocked by policyA 5.7.1 bounce means the receiving server refused your email on purpose. Learn to read bounce messages, find the real reason and fix it.
- High bounce rate: clean your mailing listSending to addresses that no longer exist damages your reputation fast. Learn the difference between hard and soft bounces and remove bad addresses after every send.
- Spam traps and bought email listsSpam traps are hidden addresses that catch senders with bad lists. Hitting them can blacklist you. Never buy lists, and only email people who asked for it.
- Emails delayed: greylisting and 4xx temporary errorsSome servers answer "try again later" on purpose. A normal mail server retries and the email arrives a few minutes late. Here is how to tell normal delays from real problems.