SMTP: 452 4.5.3 Your message has too many recipients / 452 Too many recipients received this hour
The server limits how many recipients a single message or sender may have; yours exceeded it.
452 4.5.3 Your message has too many recipientsToo many recipients received this hour452 Too many recipients452 4.5.3 Too many recipientsrecipient limit exceeded Meaning
Providers cap recipients per message (Gmail 100 via SMTP, Microsoft 365 500) and per time window. Mass mailings must be split into batches or sent through an email service provider with proper list handling.
Common causes
- Too many To/Cc/Bcc recipients in one message
- Per-hour or per-day recipient limit
- Using a personal mailbox for bulk mail
- Mailing list expanded to many addresses
- Limit on a shared hosting plan
⚡ Quick fix
- Send in batches (50-100 recipients) with pauses
- Use an ESP (SES, SendGrid, Mailgun) for bulk mail
- Check the provider's sending limits in their documentation
Detailed fix by platform
Postfix
smtpd_recipient_limit = 1000(inbound) anddefault_destination_recipient_limit = 50(outbound batches)
How to diagnose
- Limit — Provider's per-message cap?
- Window — Hourly/daily quota?
- Method — Mailbox or ESP?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 421 4.7.0 Try again later (rate limited) SMTP: 421 4.7.0 Our system has detected an unusual rate of unsolicited mail originating from your IP address. Mail sent from your IP address has been temporarily rate limited
- 450 4.7.1 Greylisted, please try again later SMTP: 450 4.7.1 <user@example.com>: Recipient address rejected: Greylisted, see http://postgrey.schweikert.ch/help/example.com.html
- 451 4.3.0 Local error in processing SMTP: 451 4.3.0 Error: queue file write error / 451 Requested action aborted: local error in processing
Most viewed in Email / SMTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 4 Nov 2026