Article

421 4.7.0 Try Again Later: What It Means and What to Do

By Unlimited Verifier Team ·

Diagram showing how a 421 4.7.0 try again later SMTP deferral leads to retries, rate-limit or reputation checks.

Summary

A 421 4.7.0 reply is a temporary SMTP deferral meaning the receiving server is refusing mail for an unnamed security or policy reason and expects a retry later. It does not mean the address is invalid. Slow your sending, read the text after the code, and only treat persistent deferrals as a reputation or blocklist signal.

A 421 4.7.0 reply is a temporary SMTP deferral: the receiving mail server is refusing your connection or message for a security or policy reason it doesn't name, and it expects you to try again later. Don't treat the address as invalid. Slow your sending, read the full text after the code, and re-check deferred addresses before deleting anything.

This page is for email marketers, list owners, agencies and SaaS teams who send or clean large lists. It explains what each part of the code means, how to tell a rate limit from a reputation problem, and how to re-check addresses that came back with this error.

Quick answer

What does "421 4.7.0 try again later" actually mean?

The code has two layers. The 421 is the SMTP reply code. RFC 5321 defines it as "Service not available, closing transmission channel," and notes it can be sent when a server must shut down or refuses to continue the session. The leading 4 marks it as a temporary failure.

The 4.7.0 is the enhanced status code, defined in RFC 3463:

Part Value Meaning
421 SMTP reply Service unavailable; connection closing; temporary
4 (class) Persistent transient failure The sender should retry later
7 (subject) Security or policy The refusal relates to a security or policy decision
0 (detail) Other or undefined The server didn't name a more specific reason

Put together, the receiving server is saying: "I won't accept this right now, for a policy or security reason I'm not specifying, so try again later."

The practical point is that 4.7.0 is a generic detail. Providers use it for rate limits, reputation throttles and anti-abuse checks, and they often add their own wording after it. Those trailing words tell you what to fix. The numbers only tell you the category.

Bottom line: 421 4.7.0 means "temporary, policy-related, come back later." Read the text after the code before deciding what it means for you.

Is a 421 4.7.0 a bounce, or a deferral that will be retried?

It is a deferral. The sending server keeps the message in its queue and retries on a backoff schedule. The sender only receives a delivery failure notice (a DSN, often shown as a MAILER-DAEMON message) if the message is still undeliverable when the queue expires.

This matters for verification. A 421 4.7.0 on a mailbox check, or on a live send, neither confirms nor rules out the address. Permanent answers come from the 5xx family, such as 550 5.1.1 user unknown. For the full split between the two classes, see 4xx versus 5xx SMTP errors.

Code Class Typical meaning Action
421 4.7.0 Temporary Undefined security or policy throttle Slow down and retry
450 4.7.1 Temporary Often greylisting, which usually clears on the next attempt Retry
550 5.7.1 Permanent Policy refusal Investigate content, authentication or reputation

Two cautions. A 421 can also mean the server is shutting down, in which case it won't carry the 4.7.0 detail. And a permanent 5.7.0 is a different thing from a temporary 4.7.0, so always check the first digit before acting.

Bottom line: a 421 4.7.0 is a deferral. Treat it as "not yet," not "never," and check the 4-versus-5 digit before making any list decision.

Which causes of 421 4.7.0 are most common?

Most 421 4.7.0 responses trace back to one of seven situations. Here are the quick picks, then the full comparison.

Cause Typical clue First action Retry? Typical duration
Gmail-hosted rate limiting "Unusual rate" wording, concentrated on one provider Lower concurrency; pause Yes, after slowing Varies
Complaint-driven deferral Text referring to user complaints Check complaints; suppress non-engagers Yes, at lower volume Varies; can run for days
Blocklisted IP or domain Often generic; check listings Find the listing; follow delisting process Yes, once the cause is fixed Until delisted
Your own connection limits Visible in your MTA logs Reduce per-domain concurrency Yes Varies
Authentication or DNS gaps Mixed; check PTR and DMARC Fix DNS records Yes, after propagation Until fixed
New IP or domain warm-up Starts when volume rises Ramp volume in steps Yes Weeks
Verification probe throttling Appears only in SMTP checks Hold as inconclusive Yes, later Varies

Bottom line: the same four characters have seven plausible causes. The table tells you which one to test first.

How did we compare these causes, and what are the limits?

We ranked each cause against four criteria: how often public provider guidance describes it, whether the error text gives a usable clue, whether the sender controls the fix, and whether the cause also affects verification.

Limitations. This article draws on public documentation, including RFCs and published sender guidelines. We did not run experiments against receiving servers, and we have no access to provider internals. Providers change their wording without notice and rarely publish a full error catalogue, so the example text quoted here may not match what you see in your logs. Microsoft-hosted recipients are less openly documented than Google's or Yahoo's sender guidance. If you're troubleshooting Microsoft bounces, the Office 365 NDR bounce codes list is a better starting point. For verifier rankings, see our guide to best email verification tools. This page doesn't compare verifiers.

Bottom line: the causes are well documented, but exact error wording and provider thresholds are not. Treat the examples as patterns, not exact strings.

What are the seven causes of a 421 4.7.0, and how do you fix each?

1. Gmail-hosted recipients rate-limiting your sending IP or domain

Gmail-hosted recipients defer mail when they see a sudden burst, a jump in volume, or a sending pattern they associate with unwanted mail. The text usually describes an "unusual rate" from your IP address. Exact wording changes over time, so match on the 4.7.0 and its surrounding sentence rather than the full string.

Most likely when: deferrals hit only Gmail-hosted addresses and cluster in one time window after a volume increase.

How to confirm: group deferrals by recipient domain and by hour. A pile-up on one provider points to that provider's throttle. If deferrals are spread across many providers, look at your own reputation and authentication first. Then compare that hour's volume with your normal pattern.

Fix: reduce concurrency to that domain, spread the send over a longer window, and let the queue drain. Google's sender guidelines set expectations for bulk senders.

Where it falls short: a rate limit doesn't say which of your sending behaviours tripped it. You have to correlate the deferral with your own send log.

Tip: some providers include a support link or short error identifier in the text. When one is present, it's the most reliable way to match your error to the provider's own explanation.

Bottom line: a Gmail rate limit is usually a volume-shape problem. Slow the send before you touch the list.

2. Complaint-driven deferrals

Some providers defer mail when recipients have been marking it as spam. Yahoo-hosted recipients have returned text referring to user complaints, sometimes with a bracketed code. Treat any specific code as provider-specific and check it against Yahoo's sender guidance.

Most likely when: deferrals persist across several sends and complaint rates have risen, often after a list import or a change in content.

How to confirm: pull complaint data from your ESP or from Google Postmaster Tools for the relevant domain. Google's sender guidelines ask bulk senders to keep the spam rate reported in Postmaster Tools below 0.1% and to make sure it never reaches 0.3%. If you're above 0.1%, the deferral is probably a symptom.

Fix: stop mailing people who haven't opened or clicked in a long time, make sure one-click unsubscribe works, and reduce frequency for unengaged segments.

Where it falls short: suppressing inactive subscribers helps reputation but doesn't remove addresses that are still bouncing. Those need separate handling.

Tip: start with your most recent 30 days of sends and compare complaint rates by segment. A single old segment, often an imported list, usually explains most of the problem.

Bottom line: a complaint-driven deferral is a reputation problem that shows up as a 421. Fix engagement, not the retry.

3. A blocklisted sending IP or domain

Some deferrals come from a listing on a blocklist. Blocklists such as Spamhaus publish their listing criteria and delisting procedures. A listing isn't always named in the 4.7.0 text, so clean-looking wording doesn't rule one out.

Most likely when: deferrals continue after you've slowed sending and the pattern doesn't clear.

How to confirm: check your sending IP and sending domain against major blocklists. Unlimited Verifier's free domain blacklist checker can screen a domain quickly.

Fix: if you're listed, fix the root cause first. That's usually a compromised account, a purchased list or a high complaint rate. Then follow the blocklist's delisting process. Requests made before the cause is fixed rarely stick.

Where it falls short: a listing explains persistent deferrals, but not the timing of the first one.

Tip: on a shared IP pool, one sender's behaviour can list the IP for everyone. Ask your provider whether the IP is shared and whether anyone else on it has been listed.

Bottom line: a blocklist explains deferrals that don't respond to slowing down. Check listings before changing your list.

4. Your own connection or concurrency limits

Sometimes the throttle is set on your side. An MTA that opens too many simultaneous connections to one provider can be told to back off, and the resulting deferrals look like a remote problem.

Most likely when: deferrals cluster in bursts that match your own send schedule, and you see a large queue for one domain.

How to confirm: on Postfix, postqueue -p lists queued messages and their deferral reasons. Filter your MTA logs for status=deferred lines to the affected domain and count simultaneous connections in the same window.

Fix: lower per-destination concurrency for that domain. Postfix exposes this as smtp_destination_concurrency_limit. Start with a conservative value and raise it only if deferrals stop without new delays. Treat this as a test, not a provider-published number.

Where it falls short: this doesn't fix a reputation issue. It only removes the burst that caused it.

Tip: if you use a shared sending platform, you may not control these settings. Ask the platform what per-domain limits it applies.

Bottom line: if your own logs show a burst, the fix is in your sending configuration, not in the recipient's policy.

5. Authentication and DNS gaps

Missing or misaligned DNS records can lead to outright rejection, and some providers defer unauthenticated mail instead. Your sending IP should have a reverse DNS (PTR) record that matches the hostname your server announces. SPF, DKIM and DMARC should be published and aligned.

Most likely when: the same deferral appears across providers, and the message headers show authentication failures or missing records.

How to confirm: check the PTR record for your sending IP, then confirm SPF, DKIM and DMARC for your sending domain. Read the authentication results in the message headers.

Fix: correct the records, allow time for DNS changes to propagate, then resend a small test batch. Google's sender guidelines set authentication and one-click unsubscribe expectations for senders who send 5,000 or more messages a day to Gmail accounts.

Where it falls short: authentication problems more often produce permanent refusals, so a 421 here is usually a secondary signal.

Tip: fix DNS even if your deferrals are provider-specific. Authentication affects every provider, and it's the cheapest fix on this list.

Bottom line: authentication is inexpensive to fix and removes one reason providers have to doubt your mail.

6. A new IP or domain that is still warming up

A fresh IP or domain has no sending history, so providers have little reason to trust it. If you send a large volume on day one, providers may defer messages until they see a steady pattern.

Most likely when: the deferrals started soon after you increased volume, and the IP or domain is new.

How to confirm: compare the start of the deferrals with your volume ramp. If volume doubled in a few days, that's your likely trigger.

Fix: increase volume in steps over several weeks, sending first to your most engaged recipients. As an illustrative example, a ramp might start at 2,000 messages a day to your most active readers and grow only after deferral rates stay flat. Warm-up schedules are a common practice, not a provider requirement, so adjust yours to your own response data.

Where it falls short: a slow warm-up delays revenue, and a fast one repeats the problem.

Tip: keep one warm-up-stage log, with daily volume and deferral rate side by side. It makes the next ramp much easier to plan.

Bottom line: new senders get throttled because providers have no history to judge them by. Ramp volume deliberately.

7. Verification probes being throttled during SMTP checks

If you verify mailboxes with SMTP checks, receiving servers see your probes and can rate-limit them the same way they limit mail. A 421 4.7.0 in this context is an inconclusive result. It says nothing about whether the mailbox exists.

Most likely when: the deferral appears only in verification output, not in your live sends, and it clusters when you probe many addresses at one domain.

How to confirm: compare your verification output with your live-send logs. If the 4xx shows up only in the probe results, you're looking at this cause.

Fix: hold the address in a separate segment. Re-check it after a delay, and spread probes across domains instead of hitting one domain in a burst. Unlimited Verifier checks syntax, domain, MX and the SMTP mailbox, and the platform upload page lets you run that check on a file. If a domain is a catch-all, a single probe is already less conclusive. Unlimited Verifier flags catch-all domains, and our catch-all email verification explainer covers why.

Where it falls short: you can't force a provider to accept more probes. You can only space them out and retry.

Tip: if your tool offers no separate holding segment, export the unresolved addresses on their own and keep them out of your Invalid list.

Bottom line: a 4xx during verification is "I couldn't tell yet." Re-check it. Don't delete it.

How do you re-check 421 4.7.0 addresses with Unlimited Verifier?

This tutorial covers the verification side: what to do with addresses that came back deferred or unresolved. Sender-side fixes are covered above.

  1. Collect the affected addresses. Filter your MTA or verifier logs for 4xx deferrals and export just those addresses into a CSV with an email column.
  2. Split the file if needed. Free lists can hold up to 150 emails, and Pro lists up to 25,000. Files must be 10MB or smaller. On Free, 1,500 addresses fit in ten lists of 150. Note that Free allows 25 lists a month, so the most you can process on Free in a month is 3,750 emails.
  3. Create a free account to start. Free includes 25 lists a month.
  4. Upload and verify the list. The email column is detected automatically.
  5. Sort the results. Valid addresses can be used. Invalid addresses should be suppressed. Risky addresses, including any that didn't reach a firm result, should be held, not deleted.
  6. Run deep verification on the Risky segment. Free includes 750 deep verifications a month, and Pro includes 25,000. Spend them on Risky addresses, not Valid ones. The company states 99.5% accuracy for its deep verification. That's a vendor claim, not an independent measurement.
  7. Export promptly. Results can be exported as CSV, Excel or JSON. Results are kept for 24 hours on Free and 30 days on Pro, so download them before the window closes.
  8. Wait, then re-check. Hold the segment for a period and re-run it. Several days is a reasonable starting point, though it's a judgement call rather than a provider rule. Standard verification is unlimited on every plan with no per-email fees, so re-checks don't add per-email cost. That matters more for retries than for per-check email verification pricing models.
  9. Automate on Pro. The email verification API accepts single checks and bulk batches of up to 10,000 emails per request, within a 100,000-email monthly API allowance. Teams building email verification API and automation into a re-check routine usually start here.
  10. For one-off addresses, use the free email checker.

Worked example (verification pass). Suppose a 40,000-recipient list returns 421 4.7.0 for 1,500 addresses on the first pass. That's 1,500 ÷ 40,000 = 3.75%. Hold all 1,500, re-check after a delay, and keep every address that clears. Deleting the whole group could remove real subscribers.

Worked example (live send). Suppose one 40,000-recipient send has 12,000 messages going to a single provider, and 960 of them are deferred and eventually expire. That's 960 ÷ 12,000 = 8% of that provider's mail, and 960 ÷ 40,000 = 2.4% of the whole send. That figure is well above the under-1% bounce target this guide recommends. Many ESPs flag hard-bounce rates around 2%, but for weekly senders we'd use the stricter 1% as the working number.

Bottom line: hold, re-check and use deep checks on the Risky segment. Don't delete on a first pass.

How do you choose the right fix for a 421 4.7.0?

Decide first whether the problem sits in your sending, your list or your verification. Then pick the fix that matches the pattern.

Your situation First fix Then
Deferrals during one large send Slow concurrency; spread the send Check the next send's deferral rate
Deferrals for several days Check complaints and blocklists Fix engagement and any listings
Deferrals only during list verification Hold as inconclusive Re-check after a delay
Deferrals on a new IP or domain Ramp volume in steps Increase over weeks, not days
Deferrals alongside authentication warnings Fix DNS Re-test after propagation

Bottom line: fix the sending pattern first when deferrals appear in live mail. Fix the verification workflow first when they appear in your check results.

What mistakes make a 421 4.7.0 worse?

For the wider set of codes you'll meet alongside this one, see the email bounce codes guide, the most common email bounce codes and how to fix them, the enhanced SMTP status codes list and common soft bounce reasons. If you also see 452 4.2.2 mailbox full or 554 5.7.1 responses, treat them as separate problems with separate fixes. For the SMTP rules behind these classes, RFC 5321 is the primary reference.

Bottom line: most mistakes come from treating a temporary code as a permanent verdict, or from retrying without changing anything.

Verdict

A 421 4.7.0 means "temporary, policy-related, try again later." It is a deferral, not a verdict on the address, and the text after the code is the best guide to the cause. Fix your sending pattern and reputation first. Then hold and re-check any addresses deferred during verification instead of deleting them.

For the verification side, a tool that sorts results into Valid, Risky and Invalid gives you a place to hold uncertain addresses. Unlimited Verifier offers unlimited standard verification on every plan, so re-checks don't add per-email cost. Start with the Free plan on this week's deferred list, and move to Pro ($25/month billed annually, or $29/month billed monthly) when you need larger lists or API access.

Bottom line: wait, re-check and fix the pattern. A 421 4.7.0 is usually recoverable.

Diagnosing a 421 4.7.0 deferral

Signal Likely cause Action
Clears within hours after volume drops Rate limit Lower concurrency, space sends out
Persists for days at low volume Reputation or blocklist Check lists, complaints, authentication
Text mentions complaints or spam Reputation Clean list, suppress unengaged users
Text mentions rate or connections Throttle Reduce connections per provider
Only one provider affected Provider-specific policy Follow that provider's postmaster guidance

Frequently asked questions

Does 421 4.7.0 mean the email address is invalid?

No. A 421 4.7.0 is a temporary 4xx response, so the address may be perfectly valid. The receiving server is only asking the sender to come back later for a policy or security reason. Do not remove addresses based on this code alone; wait and re-check, and look for permanent 5xx codes before deleting anything.

How long should I keep retrying a 421 4.7.0 message?

Keep retrying on the sending server's normal backoff schedule. Many servers retry for several days. Postfix's default queue lifetime is five days, after which the message is returned as a failure. If deferrals continue beyond that window, investigate reputation or blocklists rather than waiting longer.

What causes a 421 4.7.0 error?

Common causes include sending too many messages too quickly to one provider, poor sender reputation, spam complaints, missing or misaligned SPF, DKIM or DMARC records, and blocklist listings. The text after the code usually names the trigger, so read it before changing anything.

Should I resend immediately after getting a 421 4.7.0?

No. Manual resends can make the throttle worse and may count as further abuse. Pause or reduce concurrency to that provider, let the queue retry automatically, and only intervene if the deferral persists across several days.

How do I tell a rate limit from a reputation problem?

A rate limit usually clears within minutes or hours once volume drops, and the trailing text often mentions rate or too many connections. A reputation problem persists across days, even at low volume, and often comes with blocklist or complaint-related wording. Track the pattern over time to tell them apart.

Is 421 4.7.0 the same as 450 4.7.1?

They are related but not identical. Both are temporary 4xx responses in the 4.7 security or policy class, but the detail digit differs and providers word them differently. Both mean retry later. Read the full text after the code, since that wording is what identifies the specific policy involved.

Will a 421 4.7.0 send a bounce notice to me?

Not immediately. The sending server keeps the message queued and retries. You only receive a delivery failure notice, often a MAILER-DAEMON message, if the message is still undeliverable when the queue expires.

How do I check if my domain is on a blocklist?

Use a reputable blocklist lookup tool or your email service provider's diagnostics to check your sending IP and domain against major DNS blocklists. Also confirm SPF, DKIM and DMARC are passing and review recent spam complaint rates. Results vary by list, so check the specific provider's postmaster guidance too.

Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification

Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.

Free Pro
Price $0 $29/month ($25/month billed annually)
Lists 25 a month, up to 150 emails each Unlimited, up to 25,000 emails each
Deep verifications 750 a month 25,000 a month
API access No Yes (100,000 emails a month)
Result retention 24 hours 30 days

Why teams choose Unlimited Verifier

Unlimited Verifier states 99.5% accuracy for deep verification.

Create a free account and verify your next list before you hit send.

Want to test a single address first? Try the free email checker.