// how to fix
Gmail "550 5.4.5 Daily user sending limit exceeded": what to do
Your Gmail or Google Workspace account reached its daily sending limit. Learn the limits, how long the block lasts and how to send bulk email properly.
What it means
This is not a problem with the recipient. Your own Gmail or Google Workspace account sent more email in 24 hours than Google allows, so Google stops it from sending more for a while. The message usually looks like one of these:
550 5.4.5 Daily user sending limit exceeded. For more information on Gmail sending limits go to https://support.google.com/a/answer/166852 550 5.4.5 Daily SMTP relay limit exceeded for customer.
In Gmail itself you may instead see "You have reached a limit for sending mail". The first message concerns one user account. The second concerns the Google Workspace SMTP relay service, used by printers, websites or applications sending through Google.
Why it happens
Google limits how many messages and recipients one account can send per day. The limits change over time, but roughly:
- Free Gmail accounts: about 500 recipients per day.
- Google Workspace: about 2,000 messages per user per day, with lower limits during a trial and for external recipients in a single message.
- SMTP relay: a separate limit per user and per organization, counted in recipients.
Common reasons for reaching them:
- Sending a newsletter or mass mailing from a normal mailbox.
- A website, CRM or script using your Gmail account to send many emails.
- A compromised account sending spam.
- Many bounces to invalid addresses, which can also lower the limit or cause a suspension.
How to check
- Look at your Sent folder and, for Workspace, the email log search in the Google Admin console, to see what was sent and by which tool.
- Check account security. Look for unknown devices or app passwords in your Google account security page. Unexplained sends mean you should change the password now.
- For other tools, once you move bulk sending elsewhere, send a test email from that tool to the unique address on the Delivmail home page (
/) and check that SPF, DKIM and DMARC pass for your domain.
How to fix it
- Wait. The limit is on a rolling 24-hour window. Sending usually comes back within 24 hours. Trying to send more during this time does not help.
- Secure the account if you did not send these emails: change the password, enable two-step verification and remove unknown app passwords.
- Move bulk email to a dedicated email service. Newsletters, announcements and large notification volumes belong on an email marketing or transactional email service, not a personal mailbox.
- Authenticate that new service for your domain: add it to your single SPF record, publish its DKIM key, and keep one DMARC record for the domain.
- For the SMTP relay limit, the Workspace administrator should check which device or application is using the relay, spread its sending over time, or move it to a dedicated service.
- Clean your address lists to avoid bounces, which count against you.
Check that it is fixed
After the waiting period, send one normal email from the Gmail or Workspace account. If it goes out, the limit has reset. For the new bulk tool, send a test to a new Delivmail address and confirm the report shows authentication passing, then resend your campaign from that tool rather than from the mailbox.
Check that it is fixed
DNS changes can take from a few minutes to a few hours. Then send a new test email or scan your domain again.
Related guides
- Gmail and Yahoo bulk sender requirementsSince 2024, Gmail and Yahoo require large senders to authenticate their emails, offer one-click unsubscribe and keep spam complaints very low. Here is the checklist.
- Your emails land in Gmail's spam folderWhen Gmail sends your emails to spam, the cause is almost always authentication, reputation or content. Here is how to find which one and fix it.
- Gmail bounce "550 5.7.26": unauthenticated emailGmail refused your email because it could not confirm it comes from your domain. SPF, DKIM or DMARC is missing or failing. Here is how to fix it.
- Bounce "550 5.7.1": message rejected or blocked by policyA 5.7.1 bounce means the receiving server refused your email on purpose. Learn to read bounce messages, find the real reason and fix it.
- Add a List-Unsubscribe header (one-click unsubscribe)The List-Unsubscribe header lets Gmail, Yahoo and Outlook show an Unsubscribe button next to your sender name. Bulk senders must offer it in one click.