trustyourinbox

421 4.7.0: Gmail is temporarily deferring your mail

Gmail returns 421 4.7.0 for eight different reasons, and the code is the same for all of them. The words after it say which one you hit. Your server keeps retrying either way; here is how to read the reply and what each reason asks of you.

Verified 2026-11-02 against Google's SMTP error reference.

What the deferral means

The 4 at the front is the operative part. This is a deferral, not a rejection: Gmail told your server “not right now,” your server keeps the message in its queue, and it retries automatically over the following hours and days. Nothing has bounced yet.

What the code does not tell you is why. Google's SMTP error reference lists eight different replies under 421 4.7.0, from a sending IP with very low reputation to a recipient domain that accepts mail only over TLS. They need different fixes, and some are not yours to make. The reply text after the code is the part to read. A reputation reply, as it appears in sender logs:

421 4.7.0 This message is suspicious due to the very low reputation
of the sending IP address. To protect our users from spam, email sent
from your IP address has been temporarily rate limited.

Older Gmail replies carried a reputation deferral under 4.7.0 with wording about “an unusual rate of unsolicited mail originating from your IP address.” Google's current reference lists that unusual-rate wording under 421 4.7.28 instead, with variants for an IP, a netblock, a DKIM or SPF domain, and a URL domain. Whichever code carries it, the reputation advice below applies.

The eight reasons Google gives

Each reason below quotes Google's reply as its reference publishes it, followed by what it means and what to do. Delivery Diagnosis reads a bounce the same way: when the reply matches one of these, it names that reason.

Low sending IP reputation

This message is suspicious due to the very low reputation of the sending IP address. To protect our users from spam, email sent from your IP address has been temporarily rate limited.

Gmail rates the sending IP's reputation very low and is rate limiting it. Slow the volume, send only to people who asked for the mail, and check the IP's standing in Postmaster Tools.

Low sending domain reputation

This 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.

Gmail rates the sending domain's reputation very low and is refusing this message for now. Cut the sources of spam complaints, send only to people who asked, and check the domain in Postmaster Tools.

Suspicious content or links

This 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.

Gmail judged this message's content or links suspicious and is refusing it for now. Check every link and the wording, and drop shortened or unfamiliar link domains, before sending it again.

No matching reverse DNS

The IP address sending this message does not have a PTR record, or the corresponding forward DNS entry does not point to the sending IP. To protect our users from spam, email sent from your IP address has been temporarily rate limited.

The sending IP has no PTR (reverse DNS) record, or its PTR name does not resolve back to that IP, so Gmail is rate limiting it. Whoever runs the sending IP needs to set matching forward and reverse DNS.

Recipient domain requires TLS

TLS required for RCPT domain, closing connection.

The recipient's domain accepts mail only over TLS, and this connection did not use it. Turn on TLS (STARTTLS) on the sending server.

IP not on the recipient's allowlist

IP not in whitelist for RCPT domain, closing connection.

The recipient's domain accepts mail only from IP addresses on its allowed list, and the sending IP is not on it. The recipient's administrator has to add the IP.

Connection expired

Connection expired, try reconnecting.

Gmail closed an expired SMTP connection. The sending server reconnects and retries on its own, so there is nothing to fix unless it keeps happening.

Try again later

Try again later, closing connection. (command)

Gmail closed the connection and asked the sending server to retry later, without naming a cause. Let the retries run, and look for a pattern in volume or timing if it keeps happening.

When the reason is reputation

Three of the eight reasons are reputation: the sending IP, the sending domain, or the content and links of the message. They come from the same family of signals behind the permanent 550 5.7.28 rejection, at lower intensity: the source is sending more than its history supports, or recipients are marking the mail as spam. A big campaign to a stale list, a new IP ramping too quickly, or a compromised account leaking spam alongside your real mail all produce it. Gmail responds proportionally, and the deferral is the proportional response: enough friction to slow the mail, with the road back left open.

When the reason is setup, not reputation

The other five are about how the mail arrives, and no amount of pacing clears them.

  • No matching reverse DNS. Google's sender guidelines require valid forward and reverse DNS for the sending IP. Whoever runs that IP, your hosting provider or your email service, sets the PTR record; see reverse DNS (PTR) records.
  • TLS required for the recipient's domain. The recipient's organization accepts mail only over an encrypted connection. Turn on STARTTLS on the sending server; the TLS required page covers what to check.
  • IP not on the recipient's allowlist. The recipient's organization accepts mail only from IP addresses it has listed. That is their setting, not yours: ask their administrator to add your sending IP.
  • Connection expired, or try again later. Gmail closed the connection and expects a retry. Your server already does that; look into it only if it keeps happening.

How it clears, and what not to do

  • Let the retries work. Your server is already doing the right thing. Do not manually resend deferred messages; that adds volume and fixes nothing.
  • Fix the named reason. A setup reason clears once the setup is right. A reputation reason clears with pacing: spread large sends over hours or days and hold new campaigns until the deferrals stop.
  • Clean the list. Complaints drive the reputation reasons. Cut recipients who never engage, honor unsubscribes instantly, and do not mail anyone who did not ask for it.
  • Do not blast harder or rotate IPs. Pushing more volume through the throttle, or hopping to a fresh IP with zero history, are both spam-pattern moves that make the verdict worse instead of better.
  • Watch it persist. A reputation deferral that continues for days while you keep sending is on the escalation path to a permanent rejection such as 550 5.7.28. Treat it as the warning it is; check your complaint rate and reputation in Google Postmaster Tools rather than waiting for the hard bounce.

Frequently asked

What does 421 4.7.0 mean at Gmail?

Gmail is temporarily refusing the mail, and the code alone does not say why. Google documents eight reasons under it: low sending IP or domain reputation, suspicious content or links, a sending IP without matching reverse DNS, a recipient domain that requires TLS or accepts only allowlisted IPs, and two connection closures. The words after the code name the one you hit. The 4.x code means your mail server keeps the message queued and retries automatically.

How do I tell which reason applies?

Read the full reply in your sending server's log or the bounce message, not just the code. Each reason has its own wording, such as "very low reputation of the sending IP address" or "TLS required for RCPT domain", and the list on this page quotes every one Google publishes.

Do I need to resend messages deferred with 421 4.7.0?

No. A 4.x deferral tells your sending server to retry, and every normal mail server does so automatically for days before giving up. Manually resending on top of the automatic retries only adds volume, which makes a reputation deferral worse and fixes none of the others.

How long does the 421 4.7.0 rate limit last?

Gmail does not publish a duration, and it depends on the reason. A setup reason, such as missing reverse DNS or TLS, clears once you fix the setup. A reputation reason clears as the volume and complaint signals settle; if the behavior continues instead, it can escalate to a permanent rejection such as 550 5.7.28.

Should I switch to a different IP to get around it?

No. Rotating IPs is the signature move of a spammer and it resets you to zero reputation, which makes the throttling worse. Keep the same IP, fix the reason the reply names, and let the reputation recover where your history already lives.

Forward the bounce. Get the cause.

Send a 421 4.7.0 bounce to your workspace's diagnose address and Delivery Diagnosis reads it: the cause in plain words, the evidence from up to eight sources, what was ruled out, and a one-click DNS fix when the cause is DNS.

Was this page helpful?

Keep reading.

Start with one domain. See it with your own data.

Free for one domain, no card. Add one DNS record and the first reports usually arrive within a day.

  1. Monitoring
  2. Quarantine
  3. Reject