What it looks like in your logs
452 4.3.1 Insufficient system storage [mx.example.com]What does 452 mean?
RFC 5321 assigns 452 to a requested action not taken because of insufficient system storage. In its classic form the whole receiving server is short on disk or queue space, which blocks mail for everyone it hosts, not only your recipient. The condition is temporary and your MTA should keep retrying. Because the message was never refused on its merits, it stays in your queue. Expect your MTA to try again for a day or two before it gives up and reports a bounce.
The code is also reused for limits that are not about disk at all. Servers return 452 when you send too many RCPT TO commands in one transaction, and Gmail uses 452 4.2.2 when an individual recipient's mailbox is out of space. Large providers almost never run out of storage, so a 452 from Gmail or Microsoft is nearly always a recipient-count or quota message.
Gmail answers 452 4.5.3 when a message has too many recipients and 452 4.2.2 when the recipient's inbox is full. Self-hosted and small hosting servers are the usual source of genuine 452 4.3.1 storage errors.
Soft or hard bounce?
| Soft bounce (4xx) | Hard bounce (5xx) | |
|---|---|---|
| Nature | Temporary | Permanent |
| Sender behaviour | Queue and retry with backoff | Stop, suppress the address |
| Reputation risk | Low, unless it repeats for days | High above a 2% bounce rate |
| 452 | ✓ this code |
Common causes
- The receiving server has run out of disk or queue space.
- Your message listed more recipients in one transaction than the server accepts.
- The individual recipient mailbox is over its storage quota (452 4.2.2).
- Log files or a backed-up queue are consuming the receiving server's storage.
- A storage volume on the receiving side has failed or gone read-only.
How to fix 452
- Let your MTA retry over the next day or two; storage problems usually get fixed by the receiver's admin.
- If the text mentions too many recipients, split the message into smaller batches, for example 50 or 100 recipients per transaction.
- If the enhanced code is 4.2.2, treat it as a full mailbox and follow the advice on 4.2.2.
- For urgent mail to a small organization, reach the recipient through another channel and mention their server problem.
452 questions
What does SMTP error 452 mean?
It means the receiving server could not accept your message at that moment, originally because it lacked storage. Today it also covers too many recipients in one transaction and full mailboxes. In every case it is temporary, so the message stays in your queue and is retried.
How do I fix a 452 too many recipients error?
Send the message in smaller batches. Many servers cap recipients per SMTP transaction, and Gmail returns 452 4.5.3 when you exceed the limit. Configure your application or MTA to open a new transaction after a set number of RCPT TO commands. Bulk mail should go out one recipient per message through an ESP anyway.
What is the difference between 452 and 552?
A 452 is a temporary storage or limit problem that may clear on retry. A 552 is a permanent refusal, usually because the message itself is larger than the server allows or the mailbox has exceeded its allocation. With 452, wait. With 552, change the message or suppress the address.