Bounce errors / 421 4.7.0 Gmail
Gmail says 421 4.7.0 and holds back your email, so what should you do?
Gmail is slowing your mail down, not refusing it. Your sending server will try again by itself, so the work is on your side: send less to Gmail for a few days and fix whatever made your mail look unusual.
- Soft bounce
- Who fixes it: You
- Try again: Yes, automatically
421-4.7.0 [203.0.113.10] Our system has detected an unusual rate of unsolicited 421-4.7.0 mail originating from your IP address. To protect our users from spam, 421-4.7.0 mail sent from your IP address has been temporarily rate limited. Please 421-4.7.0 visit https://support.google.com/mail/?p=UnsolicitedRateLimitError to 421 4.7.0 review our Bulk Email Senders Guidelines. - gsmtp
You see this in a delay notice or a bounce when a lot of mail goes to Gmail addresses from one IP, domain or mailbox.
Here is how to read that message.
Each colour marks one part of the message, and the numbers match the notes underneath.
- 1The reply code421 starts with a 4, which means temporary. The server is saying not now, not never.
- 2The status code4.7.0 is a persistent transient failure in the security and policy family. RFC 3463 says the message is valid and sending later may succeed.
- 3The plain wordsGmail sees an unusual amount of mail it treats as unwanted coming from you.
- 4The resultTemporarily rate limited. Gmail slows the mail down and does not reject it.
Here are other versions of this message you may see.
The words after the code are what separate one cause from another. Find yours.
The newer wording Google lists under 4.7.28
421-4.7.28 Gmail has detected an unusual rate of email. To protect our users from spam, 421-4.7.28 email has been temporarily rate limited.
When the sending IP has a very low reputation
421 4.7.0 This message is suspicious due to the very low reputation of the sending IP address.
When the sending IP has no PTR record
421 4.7.0 The IP address sending this message does not have a PTR record ...
When your server did not use TLS
421 4.7.0 TLS required for RCPT domain, closing connection.
Here is what the message means in plain words.
A 421 is a temporary answer. RFC 3463 calls a 4 in the first position a persistent transient failure: the message as sent is valid, but a temporary condition has delayed it, and sending in the future may be successful.
Gmail uses it as a speed limit. Your volume to Gmail jumped, your mail looks like the unwanted kind, or something about the sending server is off, so Gmail accepts it slowly instead of all at once. Google lists several versions of 4.7.0 and a newer 4.7.28 for the unusual rate of email. The words after the code tell you which applies.
These are the usual reasons for it.
- A sudden jump in the number of messages going to Gmail from one IP, domain or mailbox.
- A new domain or IP that has no sending history yet.
- High spam complaints, or links and content that look like bulk unsolicited mail.
- Missing or failing SPF, DKIM or DMARC.
- The sending IP has no PTR record, or the server does not use TLS.
Here is what happens to your message while it waits.
A message that gets a 4 is not lost. It sits in your sending server's queue and goes round again.
- 1You sendYour sending server hands the message to Gmail.
- 2Gmail says not nowA 421 answer. Nothing is lost and nothing is rejected.
- 3Your server tries againIt repeats the attempt on its own schedule.
- 4It lands, or it gives upDelivered once Gmail accepts it. If the delay lasts for days, your server sends a bounce.
Who has to fix it?
The blue card is the one that fixes it. A dashed card helps in some cases, and a grey card has nothing to do.
421 4.7.0You, the sender
Fixes itYou fix it by slowing down and correcting what made your mail look unusual.
The person you emailed
Not involvedNothing to do. The recipient has not been involved yet.
Their email admin
Not involvedNothing to do. The limit is Gmail's, not a rule of the recipient's company.
Follow these steps to fix it.
- Leave the message alone.Mail servers retry a 421 automatically. Resending by hand, or adding more mail while Gmail is limiting you, makes the picture worse.
- Read the words after 4.7.0.Match them against the versions above. A rate limit, a low reputation, a missing PTR record and a missing TLS connection each have a different fix.
- Send less to Gmail for a few days.Cut the volume to Gmail addresses and spread it across the day instead of sending it in bursts. Gmail gives no fixed time, and the limit lifts as your mail stops looking unusual.
- Check your authentication.The domain health check reads SPF, DKIM and DMARC together. Google requires at least SPF or DKIM from every sender, and all three from bulk senders.
- Check your complaint rate.Google's guidance is to keep the spam rate in Postmaster Tools below 0.10% and never to reach 0.30%. A rate near that line is a common reason for a limit.
- Clean the list.Remove addresses that bounced and people who never open, and verify the rest so you are not sending to dead addresses.
- Add one-click unsubscribe to marketing mail.Bulk senders need the List-Unsubscribe headers and a visible unsubscribe link. The header generator builds them.
Here is how to stop it from happening again.
A new mailbox that sends a lot on day one is what a rate limit exists to slow down. Grow your volume in steps and Gmail has no reason to notice.
These errors look similar, and here is how they differ.
| Error | Where you see it | What it means | Try again? |
|---|---|---|---|
| 421 4.7.0 | Gmail | This page. Temporarily rate limited | Yes, automatically |
| 421 4.7.28 | Gmail | The newer wording for an unusual rate of email. Same meaning, same fix. | Yes, automatically |
| 550 5.7.1 | Gmail | The permanent version: the message is blocked as likely unsolicited. | No |
| 452 4.2.2 | Gmail | Also temporary, but the cause is the recipient's full mailbox. | Yes, later |
| 421 or 451 | Yahoo and AOL | A temporary problem on their side. Yahoo says you may retry later. | Yes, later |
These are the questions people ask about this error.
Will Gmail deliver the message in the end?
Usually yes, if a retry gets through. Mail servers keep trying for a period, and only report a bounce if the delay lasts too long.
How long does the rate limit last?
Google does not publish a time. It lifts as your sending stops looking unusual, so lower volume, passing authentication and few complaints are what bring it back.
Is 421 4.7.0 the same as 421 4.7.28?
They mean the same thing. Google lists 4.7.28 for an unusual rate of email and uses 4.7.0 for several other temporary causes, so read the words after the code.
Should I stop sending altogether?
No. Reduce the volume to Gmail addresses and keep it steady while you fix the cause. Stopping and then sending in a burst looks just as unusual.
Does a 421 hurt my sender reputation?
The error itself is a warning rather than a penalty. What it points at, such as complaints, bounces and missing authentication, is what affects your reputation.
Other bounce errors you may run into.
These are the sources behind this page.
The message wording and the fixes come from the providers' own documentation and from the RFC that defines the codes.
Ramp up without tripping the limits.
Emailchaser warms up your mailboxes and sends at a steady pace, so Gmail sees a normal sender.