Fix Gmail 421 4.7.28 and 4.7.0: Your Email Has Been Rate Limited

What the Gmail deferrals 421 4.7.28 (unusual rate of unsolicited email) and 421 4.7.0 mean, which quota you hit (IP, domain, URL or Message-ID), Google's 10-minute back-off steps, and how to fix volume, complaints and PTR.

Home › Guides › Gmail 421 4.7.28 rate limited

Last updated 18 November 2026

Quick answer

421 4.7.28 means Gmail has temporarily rate limited your mail because it saw an unusual rate of email, usually unsolicited email, from your IP address, your IP netblock, your DKIM domain, your SPF domain or a domain in your links, or too many messages with the same Message-ID. It is a temporary (4xx) reply: your server keeps the message and retries. Google's Email sender guidelines say that when you get 4.7.28:

  1. Don't send email for at least 10 minutes.
  2. Identify the cause. If the error doesn't say whether your DKIM, SPF or IP quota was exceeded, assume all three are affected.
  3. After 10 minutes, send from a single connection. If that fails, wait another 10 minutes.
  4. If it works, add connections one at a time until you're back to the number you need.

421 4.7.0 is a different family: Gmail uses that one status code for several unrelated reasons (missing PTR, a low-reputation IP, TLS or allowlist rules set by the recipient's domain, and others), so read the text after the code. Both tables below quote Google's current error reference.

The 4.7.28 messages and what each one limits

Google lists these texts for 421 4.7.28 (placeholders as Google writes them). Every one ends with To review our bulk email senders guidelines, go to Email sender guidelines or, for the last, Why has Gmail blocked my messages?

Error text (start)What is being limited
Gmail has detected an unusual rate of email. To protect our users from spam, email has been temporarily rate limited.Not stated. Treat it as all three quotas (IP, SPF domain, DKIM domain).
Gmail has detected an unusual rate of email originating from your IP address <ip-address>.The sending IP address.
Gmail has detected an unusual rate of unsolicited email originating from your IP Netblock <ip-address>.The IP range your server sends from, not just the one address.
Gmail has detected an unusual rate of unsolicited email originating from your DKIM domain <domain-name>.The domain in your DKIM signature (d=).
Gmail has detected an unusual rate of unsolicited email originating from your SPF domain <domain-name>.The domain checked by SPF (the envelope sender / MAIL FROM).
Gmail has detected an unusual rate of unsolicited email containing one of your URL domains.A domain that appears in links in the message.
Gmail has detected an unusual amount of unsolicited email originating from your IP address. ... email sent from your IP address has been temporarily blocked.The sending IP address.
Gmail has detected this sender exceeded the quota for sending messages that have the same Message-ID:. To best protect our users, the message has been temporarily rejected.Messages sharing one Message-ID.

Why the scope matters: Google says DKIM and SPF quotas are specific to your domain, so other domains sending from the same IP may not be affected. The IP quota is shared by every sender on that IP: when the IP hits its quota, all domains that send from it stop sending. That is how one noisy customer on a shared IP can defer everyone else's mail.

The permanent version, 550 5.7.28, says There is an unusual rate of unsolicited email originating from your IP address. To protect our users from spam, email sent from your IP address has been blocked. That one bounces instead of retrying.

The 421 4.7.0 messages

Same status code, different causes. These are the 4.7.0 texts in Google's reference:

CodeError text (start)What to do
421 4.7.0The IP address sending this message does not have a PTR record, or the corresponding forward DNS entry does not point to the sending IP. (rate limited)Fix reverse and forward DNS for the sending IP (below). Google also lists 451 4.7.23 for the same problem.
421 4.7.0This message is suspicious due to the very low reputation of the sending IP address. (rate limited)Reputation problem: work through the volume and complaint fixes below.
421 4.7.0This message is suspicious due to the very low reputation of the sending domain. To best protect our users from spam, the message has been blocked.Domain reputation: same fixes, and check Postmaster Tools for the domain.
421 4.7.0This message is suspicious due to the nature of the content or the links within. To best protect our users from spam, the message has been blocked.Review the content and every linked domain.
421 4.7.0IP not in whitelist for RCPT domain, closing connection.The recipient's domain only accepts mail from listed IPs. Google's guidelines describe this 4.7.0 as the sending IP not being on the allowed list for the recipient's domain. Contact the recipient's admin.
421 4.7.0TLS required for RCPT domain, closing connection.The recipient's domain requires TLS. Make sure your server offers STARTTLS to Gmail.
421 4.7.0Try again later, closing connection. / Connection expired, try reconnecting.Generic temporary errors: let your server retry.
454 4.7.0Too many sign-in attempts, try again later. / Cannot sign in due to a temporary system problem.These belong to Google Workspace's SMTP relay service, not to delivery into Gmail.

Two of these say the message has been blocked even though the reply code is 421. Under RFC 5321 a 4yz reply is a transient failure that the client SHOULD try again, so your server will normally keep retrying; fix the cause rather than waiting for the retries to succeed.

If the deferral names SPF, DKIM, DMARC, alignment or TLS instead (4.7.26, 4.7.27, 4.7.29, 4.7.30, 4.7.32, 4.7.40), it's an authentication problem: see the Gmail 5.7.26 guide.

Step 1: Find which sender and which quota

  1. Copy the full deferral from your mail server's queue or log. The text tells you whether the IP, netblock, DKIM domain, SPF domain or a URL domain is limited.
  2. Look up who else sends from that IP. On a shared IP (an email service provider, a hosting company or your own relay used by several apps), Google says the activity of every sender affects the IP's reputation. Check the IP's owner with the ASN IP Lookup.
  3. Find every service sending as your domain. Your DMARC aggregate reports list them; read them with the DMARC Report Analyzer. A forgotten app or a compromised account sending spam can use up the domain quota for everyone.
  4. Check the domain's reputation and spam rate in Google Postmaster Tools, which Google recommends for monitoring mail sent to Gmail.

Step 2: Slow down the right way

Google's advice for anyone sending large amounts of email:

Retries are normal, but they don't last forever. RFC 5321 says the retry interval SHOULD generally be at least 30 minutes and the give-up time generally needs to be at least 4-5 days. Check how long your server or provider keeps deferred mail before it bounces it.

Step 3: Cut unsolicited mail and complaints

The 4.7.28 texts mostly say unsolicited. Google's guidelines:

Step 4: Fix PTR and authentication basics

Step 5: Watch the recovery

After the 10-minute pause and single-connection test, keep an eye on your server's responses, your spam rate and your domain's reputation as you ramp back up. Google notes it can take time for spam-rate improvements to show up in spam classification. To confirm which IP and authentication results Gmail saw on a message that did get through, paste its headers into the Email Header Analyzer.

Audit hundreds of domains at once

Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).

Related tools and guides

Check PTR and forward DNS with the DNS Lookup, authentication with the Email Deliverability Checker, every sender in your DMARC reports with the DMARC Report Analyzer, the owner of a sending IP with the ASN IP Lookup and a delivered message with the Email Header Analyzer. Related guides: Gmail 550 5.7.26 and the authentication deferrals, Gmail, Yahoo and Outlook bulk sender rules, Gmail 550 5.7.1 (message blocked) and Yahoo and AOL 554 5.7.9.

FAQ

What does Gmail 421 4.7.28 mean?

Gmail has temporarily rate limited your mail because it detected an unusual rate of email, usually unsolicited email, from your IP address, IP netblock, DKIM domain, SPF domain or a domain in your links, or too many messages with the same Message-ID. Your server keeps the message and retries.

How long should I wait after a 4.7.28 error?

Google says to stop sending for at least 10 minutes, find the cause, then send from a single connection. If that fails wait another 10 minutes; if it works add connections one at a time.

Is 421 4.7.0 the same as 4.7.28?

No. Gmail uses 4.7.0 for several unrelated reasons, including a missing or mismatched PTR record, a low-reputation IP or domain, suspicious content, and TLS or IP allowlist rules set by the recipient domain. Read the text after the code to see which one applies.

Does a 4.7.28 on a shared IP affect other senders?

Yes, for the IP quota. Google says the IP address quota is shared by every sender on that IP, so when it is reached all domains sending from that IP are limited. SPF and DKIM domain quotas only affect your own domain.

Will my mail be delivered eventually?

A 421 reply is temporary, so your server retries. RFC 5321 suggests retrying at least 30 minutes apart for at least 4 to 5 days, but if the cause is not fixed the retries keep failing and the message eventually bounces.

Want the full kit?

Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.