Map Extract

A 421 4.7.0 or 421 4.7.28 reply from Gmail is a deferral, not a bounce: Gmail refused the message for now and told your server to try again later. The text after the code says why. TLS and PTR problems are configuration you can fix in minutes; "low reputation" and "unusual rate" mean you are sending more, or less wanted, mail than Gmail will take from you, and the only fix is to pause and send less. Ignore them and Gmail moves on to 5xx rejections.

This page is part of our SMTP error codes guide for cold email.

The variants and what triggers each

Gmail's published error list has many 421 lines. They fall into four groups.

1. Transport and configuration

Code and text (Gmail's wording)TriggerFix
421 4.7.0 TLS required for RCPT domain, closing connection.The recipient domain requires TLS and your server did not use itEnable STARTTLS on the sending server
421 4.7.29 Your email has been rate limited because you're not using a TLS connection.No TLS; Google requires all senders to use TLSEnable STARTTLS
421 4.7.0 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.Missing or mismatched reverse DNSAsk your host to set a PTR whose hostname resolves back to the IP
421 4.7.0 IP not in whitelist for RCPT domain, closing connection.A Workspace recipient only accepts mail from listed IPs (for example, behind a gateway)Nothing you can change; contact the recipient another way

2. Reputation of the IP, domain or content

Code and textTrigger
421 4.7.0 This message is suspicious due to the very low reputation of the sending IP address.Your IP's reputation at Gmail
421 4.7.0 This message is suspicious due to the very low reputation of the sending domain.Your domain's reputation at Gmail
421 4.7.0 This message is suspicious due to the nature of the content or the links within.Content or a linked domain

3. Unusual rate (421 4.7.28)

Every 4.7.28 line starts "Gmail has detected an unusual rate of" and names what Gmail is counting:

Text namesMeaning
"email" (no qualifier)Overall volume spike from you
"email originating from your IP address"Volume from one IP
"unsolicited email originating from your IP Netblock"Volume of unwanted mail from your IP range, which can include neighbours on shared hosting
"unsolicited email originating from your DKIM domain" or "SPF domain"Volume of unwanted mail tied to your domain wherever it is sent from
"unsolicited email containing one of your URL domains"A domain in your links, such as a tracking domain
"exceeded the quota for sending messages that have the same Message-ID"Resending the identical message repeatedly

IANA registers X.7.28 as "Mail flood detected", which is a fair summary. The word "unsolicited" matters: it means Gmail's users are marking the mail as spam or ignoring it, not only that there is a lot of it.

4. Authentication rate limits

421 4.7.26 (unauthenticated), 421 4.7.27 (SPF did not pass), 421 4.7.30 (DKIM did not pass), 421 4.7.32 (From not aligned) and 421 4.7.40 (no DMARC record) are deferrals caused by authentication. Fix them as described in Gmail 550-5.7.26 unauthenticated sender; retrying without the fix only collects more deferrals.

The generic 421 4.7.0 Try again later, closing connection. gives no reason. Treat it as a rate or reputation deferral unless TLS or PTR is obviously missing.

Deferral versus block: why the retry queue matters

RFC 5321 says a 4yz reply means "the error condition is temporary" and "the SMTP client SHOULD try again". A properly configured mail server keeps the message in its queue and retries. A sending tool that treats every non-250 reply as a failure, or that retries instantly in a loop, gets this badly wrong in both directions:

  • Treating 421 as a bounce loses mail and marks good addresses as bad.
  • Retrying immediately sends the same volume Gmail just refused, which deepens the rate limit. Google's guidance for 4.7.28 is "Do not send email for at least 10 minutes", then resend from a single connection and increase gradually, and in general to "reduce the sending volume until the SMTP error rate decreases".

There is a cold email twist. RFC 5321 suggests general mail servers retry for "at least 4-5 days". A cold message that arrives four days late is stale, and every retry spends reputation. For outreach, retry within a day and then let the message expire.

A safe backoff schedule

A schedule for one deferred cold message to a Google-hosted recipient:

AttemptWait since previous attemptNotes
1Original sendDeferred with 421
215 to 30 minutesSame server, same envelope sender
31 hour
42 hours
54 hours
68 hoursLast attempt for a cold message
StopAbout 24 hours after the first attemptRecord as expired, not as a hard bounce; do not mark the address invalid

RFC 5321 says the retry interval "SHOULD be at least 30 minutes" for a general server, so the 15-minute first step is only appropriate for a single message. When the deferral names your IP or domain, schedule matters less than the campaign-level pause below: individual retries should not start until the provider-wide pause is over.

Throttle per receiving provider, not per domain

Gmail rate limits by sender, but it receives mail for gmail.com and for every business domain on Google Workspace. A list of 500 "different" company domains may have 200 that point their MX records to Google. Throttling per recipient domain misses this.

Group recipients by mail provider before you set rates:

  1. Look up the MX record for each recipient domain. Hosts ending in google.com or googlemail.com are Google.
  2. Group Microsoft 365 recipients (MX ending in mail.protection.outlook.com) and any gateways (Mimecast, Proofpoint) separately.
  3. Give each provider its own hourly budget, and pause the whole provider group when one deferral names your IP or domain.
SignalAction for the Google group
One 421 4.7.0 with TLS or PTR textFix configuration; no need to pause others
A few 421 4.7.28 or reputation deferrals in an hourPause the Google group for the rest of the day
Deferrals return on the next day at lower volumeHalve the daily budget, review targeting and content, check complaints
Any 550 5.7.28 or 550 5.7.1 rejectionStop the Google group entirely and investigate before sending again

Postmaster Tools signals to watch

Google Postmaster Tools is where Gmail reports how it sees your domain. Add and verify your sending domain, then watch:

  • Spam rate. Google's guidelines say to keep the rate reported in Postmaster Tools below 0.3%, aim for under 0.1%, and "avoid ever reaching a spam rate of 0.30% or higher". A rising spam rate is the usual reason for 4.7.28 "unsolicited" deferrals.
  • Authentication results for SPF, DKIM and DMARC, to confirm the alignment you think you have.
  • Compliance status against the sender guidelines, if shown for your domain.

At low daily volumes Postmaster Tools may show little or no data for your domain. Lack of data is not a clean bill of health; use replies, complaints and bounce trends as well. The spam rate thresholds are explained in Gmail and Yahoo bulk sender requirements.

When deferrals become 5xx blocks

Gmail escalates when the cause persists:

DeferralEscalates to
421 4.7.28 unusual rate from your IP550 5.7.28 There is an unusual rate of unsolicited email originating from your IP address.
421 4.7.0 low reputation or content550 5.7.1 This message is likely unsolicited email. Paste it into the SMTP error code lookup
421 4.7.0 no PTR record550 5.7.25 This message was blocked because the sending IP address doesn't have a PTR record
421 4.7.29 no TLS550 5.7.29 This message was blocked because it wasn't sent over a TLS connection.
421 4.7.40 no DMARC record550 5.7.40 (bulk senders without DMARC)

The other route to a bounce is time: your server keeps retrying until its give-up time, then returns the message to you as undeliverable with the last 421 text inside. That is still a deferral cause, not a bad address.

Yahoo has an equivalent family of deferrals (421 4.7.0 [TSS04] and related codes); the SMTP error code lookup reads them too. If the deferral says "Greylisted", it is a different mechanism; see 451 4.7.1 greylisted.

How Map Extract helps

Map Extract's bulk email sender is built for the low, steady volumes that avoid Gmail deferrals in the first place:

  • Pacing controls. Hourly, daily and monthly campaign caps, a minimum delay between messages, per-route ceilings per hour and day, and an optional warm-up ramp that starts low and rises by a set amount every set number of minutes.
  • Automatic pause on bounces. Bounces are read over IMAP, and the campaign pauses itself when they reach the threshold (5% by default), which stops a deferral problem from becoming a run of 5xx rejections.
  • Accepted, queued and uncertain are separate states. The outbox does not count a deferred message as sent, and an uncertain send is not resent automatically, which avoids duplicate messages that can trigger the same-Message-ID quota.
  • Reviewed audiences. Recipients come from reviewed records with a recorded permission basis and suppression checks, which keeps "unsolicited" signals down.

What it does not do: Map Extract's documentation does not describe automatic per-provider grouping by MX or a configurable backoff schedule for 4xx deferrals. Use the caps and the pause, check the outbox before resuming, and group your audience by provider yourself if a large share is on Google. It also does not configure TLS or PTR on your mail server.

Key takeaways

  • 421 means try again later; the text says whether it is TLS, PTR, reputation or rate.
  • Fix TLS and PTR at once; for reputation and rate, pause and send less.
  • Google says wait at least 10 minutes after 4.7.28; for cold email, pause Google recipients for the day.
  • Throttle by receiving provider: Workspace business domains share Gmail's limits.
  • Unfixed deferrals escalate to 550 5.7.28, 5.7.1 or 5.7.25 rejections.

Frequently asked questions

What does 421 4.7.0 try again later mean from Gmail?

It is a temporary deferral: Gmail did not accept the message this time and closed the connection, but you may retry later. The text that follows says why, for example missing TLS, a missing PTR record, or low reputation of the sending IP or domain. Your server should keep the message queued and retry on a backoff schedule rather than treat it as a bounce.

How long should I wait after a 421 4.7.28 unusual rate error?

Google's sender guidance says not to send email for at least 10 minutes, then resend from a single connection and increase volume gradually. For a cold campaign, a longer pause is wiser: stop sending to Google-hosted recipients for the rest of the day, lower the hourly cap and resume the next day at a reduced rate while watching for repeat deferrals.

Will Gmail deferrals turn into permanent bounces?

They can. If the cause is not fixed, Gmail moves from rate limiting to rejection: 421 4.7.28 unusual rate deferrals can become 550 5.7.28 or 550 5.7.1 unsolicited mail rejections, and PTR-related 421 4.7.0 deferrals can become 550 5.7.25. A message your server retries for days will also eventually expire and bounce back to you as undeliverable.

Does 421 4.7.0 affect Google Workspace addresses too?

Yes. Business domains that use Google Workspace receive mail through the same Gmail infrastructure, so a deferral from Gmail can affect recipients at many company domains, not only gmail.com. Check the MX records of your recipients: if they point to Google, count them together when you throttle and when you pause after a deferral.

Sources

  1. Google Workspace: Gmail SMTP errors and codes
  2. Google: Email sender guidelines
  3. RFC 5321: Simple Mail Transfer Protocol
  4. IANA: SMTP Enhanced Status Codes registry

Written by the Map Extract editorial team. Found an error? Email support@mapextract.uk and we will check and correct it. How we research guides: editorial policy.

See it working on your own searches.

Start with one keyword, one location and a small limit. Review the records, then decide on a licence.

Top