# SMTP 452: insufficient system storage or too many recipients URL: https://iblockspam.com/smtp-errors/452 Last updated: 2026-10-09 Code: 452 (temporary failure, the sender retries) Provider: Standard (RFC) The receiving server can't accept the message right now because of a storage limit, or because the message has more recipients than it takes in one go. What the bounce says: ``` 452 4.5.3 Your message has too many recipients. ``` Start of Gmail's text for this case, as listed in Google's SMTP errors reference. RFC 5321 defines 452 as "Requested action not taken: insufficient system storage". It is temporary: the condition may clear, so the sender retries. The same code covers too many recipients. RFC 5321 explains that RFC 821 listed the "too many recipients" error as 552 by mistake and that the correct reply is 452. A conforming server already has at least 100 recipients buffered when it sends this reply, and the sending server is expected to deliver the rest in another transaction. Gmail returns 452 4.5.3 for too many recipients, and 452 4.2.2 when a recipient's inbox is out of storage space. So a 452 has three likely meanings: the server's disk is full, the recipient's mailbox is full, or your message had too many recipients for one transaction. The enhanced code tells you which: in the IANA registry, X.2.2 is "Mailbox full", X.5.3 is "Too many recipients" and X.3.1 is "Mail system full". ## Common causes - The recipient's mailbox is over its storage quota. - The message lists more recipients than the server accepts in one transaction. - The receiving server is low on disk space. ## How to fix it (sender) - For too many recipients: let your server split the delivery, or send to smaller groups or a mailing list. - For a full mailbox: wait, or contact the recipient another way so they can clear space. ## How to fix it (recipient or admin) - Delete or archive mail to get back under your quota, or ask your admin for more storage. - If your server sends 452 to everyone, check free disk space on the mail store and queue. **Q: Why did I get 452 for too many recipients and not 552?** RFC 5321 says 452 is the correct code for too many recipients, because the sender can deliver the remaining recipients in another transaction. Some older servers still send 552 for this, and RFC 5321 tells clients to treat that 552 as temporary. **Q: Does a 452 mean the recipient's mailbox is full?** Sometimes. Gmail uses 452 4.2.2 when the recipient's inbox is out of storage. Other 452 replies mean too many recipients or a full server disk, so check the enhanced code and text. Sources: - RFC 5321: Simple Mail Transfer Protocol (reply codes, section 4.2): https://www.rfc-editor.org/rfc/rfc5321#section-4.2 - RFC 5321, section 4.5.3.1.10: Too many recipients code: https://www.rfc-editor.org/rfc/rfc5321#section-4.5.3.1.10 - IANA: SMTP Enhanced Status Codes registry: https://www.iana.org/assignments/smtp-enhanced-status-codes/smtp-enhanced-status-codes.xhtml - Gmail SMTP errors and codes (Google Workspace Admin Help): https://knowledge.workspace.google.com/admin/support/troubleshooting/gmail-smtp-errors-and-codes --- Source: iBlockSpam, https://iblockspam.com/smtp-errors/452 (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt