452 4.2.2: the recipient's inbox is out of storage space
The recipient's Google account is out of storage, so Gmail is temporarily refusing new mail. Your server will retry; delivery succeeds once the recipient frees space.
452 4.2.2 The recipient's inbox is out of storage space. Please direct the recipient to Manage files in your Google Drive storage.
The 452 4.2.2 message in Google's Gmail SMTP errors and codes reference.
What 452 4.2.2 means
Google lists 452 4.2.2 with the text "The recipient's inbox is out of storage space." It's a temporary failure: your server keeps the message and retries. RFC 3463 defines X.2.2 as "Mailbox full" and says it should be used as a persistent transient failure, because the recipient can delete messages to make space.
Google storage is shared. Google says each Google Account includes up to 15 GB, shared across Gmail, Google Drive and Google Photos, and that going over quota can affect the ability to send and receive email. So the recipient may need to delete large Drive files or photos, not just old emails, or buy more storage.
If the recipient doesn't free space, the retries eventually fail. Google also lists a permanent 552 5.2.2 message for an inbox that is out of storage space and inactive; that one bounces at once. Google warns that an account over quota for 2 years or longer can have its content removed.
Likely causes
- The recipient's Google account storage (Gmail, Drive and Photos combined) is full.
- Large attachments or files filled the shared quota.
How to fix it
If you sent the message
- Let your server retry; it will deliver once space is freed.
- Tell the recipient another way that their Google storage is full.
- Avoid resending large attachments; share a link instead.
If you're the recipient or their admin
- Delete large emails, Drive files or photos, and empty the trash so the space is released.
- Check storage use in your Google account and buy more storage if you need it.
Frequently asked questions
Will my email arrive after a Gmail 452 4.2.2 storage error?
It can. A 452 is temporary, so your server keeps retrying. If the recipient frees space before your server's retry period ends, the message is delivered. If not, you get a final bounce.
Why is a Gmail inbox full when the recipient has few emails?
Google storage is shared across Gmail, Google Drive and Google Photos. Large files or photo backups can use up the quota, which also blocks incoming mail.
Sources
- Gmail SMTP errors and codes (Google Workspace Admin Help)
- How your Google storage works (Gmail Help)
- Fix bounced or rejected emails (Gmail Help)
- RFC 3463: Enhanced Mail System Status Codes
Provider messages are quoted as the provider publishes them. Servers can change their wording, so the bounce you received may differ slightly.
Related codes
- 552 5.2.2 552 5.2.2: mailbox full
- 452 SMTP 452: insufficient system storage or too many recipients
- 550 5.2.1 550 5.2.1: the email account that you tried to reach is inactive
- 553 5.1.7 553 5.1.7: the sender address is not a valid RFC 5321 address
- 550 5.7.28 550 5.7.28: unusual rate of unsolicited email from your IP
- 550 5.7.24 550 5.7.24: the sending domain's SPF record has suspicious entries
- 553 5.1.2 553 5.1.2: we weren't able to find the recipient domain
Related guides
Hard bounce vs soft bounce: what's the difference and what should you do?
The difference between hard and soft email bounces, how RFC 3463 status codes classify them, when to retry or remove an address, and how to keep lists clean.
9 min read Phishing & threatsMailbox full and account suspended phishing: how to spot and stop it
How 'mailbox full', 'account suspended' and 'email upgrade' phishing works, and how to check real mailbox storage in Microsoft 365 and Google Workspace.
8 min read Running email day to dayWhat happens to email when your mail server is down?
Senders retry when your mail server is down, but not forever. How SMTP retries work, 4xx vs 5xx errors, what senders see, and how outage spooling helps.
8 min read