Gmail 550 5.4.5: “Daily user sending limit exceeded”
Short answer: Your own Gmail or Google Workspace account hit its daily sending limit, so Google stopped sending for you; no recipient blocked you. Sending resumes within 24 hours. For newsletters or other bulk mail, use a sending service instead of a mailbox.
550 5.4.5 Daily user sending limit exceeded. For more information on Gmail sending limits, go to …
550 5.4.5 Daily user sending quota exceeded. … - gsmtp
You have reached a limit for sending mail.
550 5.4.5 Daily SMTP relay limit exceeded for user.
What it means
The block is on your own account: once it passes a daily limit, Google stops it from sending for up to 24 hours, counted over a rolling 24 hours. Personal Gmail: about 500 emails a day, or 500 recipients in one message. Google Workspace: 2,000 messages a day per user (500 on trial accounts, 1,500 with mail merge), 10,000 recipients a day in total, 2,000 different external recipients a day, and 100 recipients per message when an app sends over SMTP. Every To, Cc and Bcc address counts, and so does mail sent from aliases, by delegates or by the vacation responder. Google notes the limits can change without notice. The SMTP relay lines refer to the separate limit of Workspace's smtp-relay service.
How to fix it
- Wait: sending comes back by itself within 24 hours (Google says 1 to 24 hours for personal Gmail). You can still receive mail meanwhile.
- Pause scripts, mail merges and apps that send through the account until the limit resets. Then spread the remaining mail over several days.
- Count what you really send: a message to 50 people uses 50 of the recipient limit, and aliases, delegates and auto-replies share the same limit.
- Workspace trial? Trial accounts keep the lower limits until the domain has paid at least US$100 in total, which can take up to 75 days.
- For newsletters, announcements or app notifications, use a sending service instead of a mailbox, for example Amazon SES, Postmark or Brevo. For a small group of people, Google suggests a Google Group.
- When you move bulk mail to a service, add it to SPF (SPF generator) and turn on its DKIM with your domain, or Gmail recipients will reject it with 5.7.26 instead.
- SMTP relay variant: your Workspace admin can see the relay's sending limits in the SMTP relay service settings.
Check your domain now
After the fix, send a test email to see SPF, DKIM and DMARC pass on a real message, then keep an eye on it: free DMARC monitoring shows every service that sends mail as your domain and which ones fail, in plain English.
Get it fixed on Fiverr
Prefer to do it yourself? Get the step-by-step Fix Kit ($15) – 28-page guide, checklist, 20+ providers.
Other bounce errors
- Gmail 550 5.7.26
- Gmail 421 4.7.26
- Gmail 550 5.7.27 / 421 4.7.27
- Gmail 550 5.7.30 / 421 4.7.30
- Gmail 550 5.7.32 / 421 4.7.32
- Gmail 550 5.7.40 / 421 4.7.40
- Gmail 550 5.7.24 / 421 4.7.24
- Gmail 550 5.7.25 / 421 4.7.23
- Gmail 550 5.7.29 / 421 4.7.29
- Outlook / Hotmail 550 5.7.515
- Outlook / Hotmail 550 5.7.1 S3150 / S3140
- Microsoft 365 550 5.7.606 / 5.7.511
- Microsoft 365 / Outlook 550 5.7.509
- Outlook / Hotmail 451 4.7.650 (S775)
- Yahoo / AOL 421 4.7.0 [TSS04]
- Yahoo / AOL 553 5.7.1 [BL21] / [BL23]
- Yahoo / AOL 554 5.7.9
- Gmail 421 4.7.28
- Microsoft 365 550 5.7.708
- Microsoft 365 535 5.7.139 / 530 5.7.57
- Microsoft 365 550 5.7.233 / 5.7.232
- Microsoft 365 550 5.7.236
- Microsoft 365 / Outlook 550 5.7.520
- Microsoft 365 550 5.1.8
- Gmail 550 5.7.1 / 421 4.7.0
- Gmail 550 5.7.1 / 421 4.7.0
- Gmail / Yahoo / iCloud 550 5.7.26 / 554 5.7.9 / 554 5.7.1 [BS01]
- Validity Heatwave domain blocklist