WarningSMTP Error · Permanent (5.x.x)
5.2.2

Mailbox full or submission quota exceeded

5.2.2 has two meanings. Most mail servers use it when the recipient's mailbox is full. Microsoft 365 also uses it for "Submission quota exceeded": the sender went over Microsoft's sending limits.

Updated June 13, 2026

SMTP Exchange / Mail Log
> MAIL FROM:<you@yourdomain.com>> RCPT TO:<recipient@example.com>✕ 5.2.2 Mailbox full or submission quota exceeded
All guides

Is your domain affected?

Run a free check — we'll show you exactly what's misconfigured.

5.2.2 is a permanent SMTP reply meaning mailbox full or submission quota exceeded. If the bounce mentions a full mailbox or QuotaExceeded, the problem is on the recipient's side. If it says "Submission quota exceeded", the problem is on your side: Microsoft says the sender exceeded the recipient rate limit or the message rate limit, and that it can also mean the account was compromised.

What 5.2.2 means

If the bounce mentions a full mailbox or QuotaExceeded, the problem is on the recipient's side. If it says "Submission quota exceeded", the problem is on your side: Microsoft says the sender exceeded the recipient rate limit or the message rate limit, and that it can also mean the account was compromised.

⚠️
This is a 5.x.x permanent failure — the message will keep bouncing until you fix the cause. Retrying the same message unchanged won't help.

Common causes

📨
#1

The recipient mailbox is full

Most common

The person has used all their storage. Mail will bounce until they delete mail or get more space.

🔁
#2

You hit Microsoft 365 sending limits

Common

Microsoft 365 limits how many recipients and messages one mailbox can send per minute and per day.

⚙️
#3

A compromised account is sending spam

Less common

A sudden burst that hits the limit can mean someone else is using the account.

How to fix 5.2.2

  1. 1

    Read which 5.2.2 you got

    Mailbox full: contact the recipient another way or try later. Submission quota exceeded: the fix is on your side.

  2. 2

    Stay under the sending limits

    Spread sends over time, or send bulk mail through a sending service instead of a Microsoft 365 mailbox.

  3. 3

    Check the account if the volume was unexpected

    Look for unknown sent items, inbox rules and sign-ins, and secure the account.

Confirm your domain is set up correctly

Most delivery failures — permanent or temporary — trace back to authentication or reputation. Run a free EmailHealth check to confirm SPF, DKIM, DMARC, blacklist status, and TLS are all healthy for your sending domain. If you send in volume, free daily monitoring will alert you before a small issue becomes a flood of bounces.

Stop this error from coming back

Most delivery problems start when a DNS record changes, a key is removed or a domain lands on a blocklist. EmailHealth checks your sending domains every day and sends one alert, by email, Slack or webhook, with the exact fix.

1 domain free. Sending from many domains (cold email, agencies, MSPs)? Early access covers 10.

Frequently asked questions

Check your domain for free

SPF, DKIM, DMARC, MX, blocklists and TLS in about 2 seconds. No account needed.

Run the check