schedule 10-min read

Tempfail and 4xx Deferrals: What Senders Should Check

DMARC AI editorial team · Last updated

What a tempfail or 4xx deferral means, how SPF and DMARC temperror differ, real Gmail, Yahoo and Microsoft codes, and a triage order for MSPs.

01

Introduction

A tempfail is a temporary SMTP failure: the receiving server answers with a 4xx reply code, the message is not delivered yet, and your server queues it and tries again later. A 4xx deferral is a delay, not a bounce. It only becomes a bounce if the cause persists until your server gives up.

The useful question is what caused it. Sometimes it is a DNS problem with SPF, DKIM or DMARC that you can fix in minutes; more often it is reputation or rate limiting, which no DNS change will touch. This guide gives MSPs a triage order for both. Permanent codes are covered in our guides to Gmail 550 5.7.26, Yahoo TSS04 and Microsoft 550 5.7.515; the protocol background is in the DMARC guide.

02

Key takeaways

  • A 4xx reply means "try again later"; a 5xx reply means "do not repeat this request". RFC 5321 suggests a retry interval of at least 30 minutes and a give-up time of at least 4 to 5 days.
  • SPF temperror is a transient DNS problem; SPF permerror is a broken record, including more than 10 DNS lookups. Only the first is a genuine tempfail.
  • RFC 9989 leaves DNS errors during DMARC checks to the receiver, which may deliver the message or answer with a 4xx reply.
  • Most provider deferrals (Gmail 421 4.7.28, Yahoo TS*, Microsoft 451 4.7.500-699) are about rate, reputation or suspicious activity, not records.
  • RFC 9990 does not say whether mail deferred during the SMTP session appears in DMARC aggregate reports, so do not use them to measure deferrals.
03

What is the difference between a temporary and a permanent SMTP failure?

The first digit of the reply code decides it. RFC 5321 defines a 4yz reply as a temporary error where "the action may be requested again", and a 5yz reply as one where the client "SHOULD NOT repeat the exact request". Your server retries a 4xx message and returns a 5xx message to the sender.

The enhanced status code follows the same split. RFC 3463 calls class 4 a "persistent transient failure" and class 5 a failure "not likely to be resolved by resending the message in the current form".

Part of the reply Example What it tells you
Reply code 421, 450, 451, 452 Temporary; the server will retry
Reply code 550, 553, 554 Permanent; the message comes back
Subject digit 4.4.x (network and routing), 4.7.x (security or policy) Area of the problem
Provider text "unusual rate of unsolicited email" The actual reason; always read it

The text matters most. Two 421 4.7.0 replies from Gmail can mean a missing PTR record or a very low IP reputation, which need completely different fixes.

04

How long do sending servers keep retrying a deferred message?

RFC 5321 section 4.5.4.1 says "the retry interval SHOULD be at least 30 minutes" and "the give-up time generally needs to be at least 4-5 days". Real platforms use their own schedules, so check the sending platform's queue settings.

When the give-up time is reached, the message bounces. Exchange Online reports this as 4.4.7 Message expired in Microsoft's NDR reference. That is why a user can report a "bounce" days after sending: the real event was a deferral.

05

What is the difference between temperror and permerror in SPF and DKIM?

A temperror means the check could not finish because of a transient fault, usually a DNS timeout. A permerror means the published record cannot be interpreted. RFC 7208 says a later retry of a temperror "may succeed without further DNS operator action", while a permerror "definitely requires DNS operator intervention".

The SMTP replies RFC 7208 recommends show the difference clearly:

SPF temperror, rejected in session:  451 4.4.3  (temporary, will be retried)
SPF permerror, rejected in session:  550 5.5.2  (permanent)

A common trap is the lookup limit: more than 10 DNS-querying terms, or more than two "void lookups" (queries returning no answer), returns permerror. That is a broken record, not a tempfail, and it fails SPF for every message. SPF too many DNS lookups shows how to flatten or restructure the record.

DKIM works the same way: RFC 6376 defines TEMPFAIL as "a temporary, recoverable error such as a DNS query timeout".

06

What does DMARC do when DNS lookups fail?

RFC 9989 lists temperror in its result registry (Section 9.2) for transient problems such as an unreachable DNS server, but it does not prescribe what the receiver does next. Section 4.10.1 says handling of DNS errors when fetching the policy record "is left to the discretion of the Mail Receiver", which can "fail open" and deliver, or "fail closed" with "an SMTP 4yx reply". If queries do not complete, the message "cannot be considered to pass or fail".

So a missing record and an unreachable record are different: with no record, receivers must not apply DMARC; with a timeout, the receiver decides. Gmail documents the deferral case:

451 4.7.26 Unauthenticated email from [domain-name] is not accepted due to
domain's DMARC policy, but temporary DNS failures prevent authentication.

When you see it, check the client's DNS hosting: slow or failing authoritative servers, a lapsed zone or a provider outage. A permanent 554 5.7.5 rejection is different: it usually points to a malformed or duplicated DMARC record rather than a DNS outage, as explained in 554 5.7.5 permanent error evaluating DMARC policy.

07

Which deferral codes do Gmail, Yahoo and Microsoft document?

Each provider documents its temporary codes, and most point at rate, reputation or behaviour rather than records. Google's Gmail SMTP errors and codes page is the most detailed; Yahoo documents families and Microsoft documents ranges.

Provider Code Documented meaning Fix in DNS?
Gmail 421 4.7.0 No PTR or mismatched forward DNS, very low IP or domain reputation, suspicious content, or TLS required Only the PTR variant
Gmail 451 4.7.23 Sending IP has no matching PTR record Yes (reverse DNS)
Gmail 451 4.7.26 DMARC policy applies, but temporary DNS failures prevent authentication Yes (DNS hosting)
Gmail 421 4.7.26, 4.7.27, 4.7.30, 4.7.32, 4.7.40 Rate limited because of failing SPF, DKIM, alignment or a missing DMARC record Yes
Gmail 421 4.7.28 "Unusual rate of unsolicited email" from your IP, netblock, DKIM domain, SPF domain or a URL domain No
Gmail 421 4.4.5 / 451 4.4.2 "Server busy, try again later." / "Timeout – closing connection." No
Yahoo TS* Complaints, objectionable content, poor IP or subnet reputation, unusual traffic No
Yahoo 421 / 451 Unusual traffic, complaints, busy servers, an unavailable name server, or authentication results that could not be determined Sometimes
Yahoo 451 (unresolvable From domain) SOA lookup for the MAIL FROM or header From domain timed out or returned SERVFAIL Yes
Microsoft 451 4.7.500-699 "Access denied, please try again later": suspicious activity, sending temporarily restricted No

Notes on reading these:

  • Gmail appends gsmtp to all its errors. The 4.7.x authentication codes are twins of the permanent 5.7.x codes in the Gmail guide: a warning before rejection.
  • Yahoo's SMTP error codes page groups deferrals as "TS* Errors" and does not define TS01, TS02, TS03 or TSS04 individually. Yahoo checks domain existence "by using an SOA query". The Yahoo guide covers the full list.
  • Microsoft says the 4.7.500-699 restriction is lifted "shortly" if the traffic is valid. In practice the reply often reads "451 4.7.500 Server busy. Please try again later" with a bracketed AS code; its external sender troubleshooting page gives 451 4.7.550 as the throttled-IP example.
08

When is authentication actually the cause of a deferral?

Authentication is the cause when the reply text names SPF, DKIM, DMARC, a PTR record or a DNS failure, as Gmail's 4.7.23, 4.7.26 to 4.7.32 and 4.7.40 codes do. Replies about rates, reputation, complaints or suspicious activity are not fixed in DNS. A quick way to tell them apart:

  1. The text names a control ("SPF", "DKIM", "DMARC", "PTR", "DNS failures"): fix that control.
  2. The text names a rate or reputation ("unusual rate", "low reputation", "suspicious activity", "too quickly"): look at volume, lists and content.
  3. The text is generic ("server busy", "try again later"): watch whether it clears on retry before acting.
09

In what order should an MSP triage deferrals across client domains?

Rule out the cheap DNS causes first, then move to volume and reputation. DNS checks take minutes and sit within an MSP's control; reputation work involves the client and often a third-party email platform.

Step Check Tool or source Points to
1 Capture the full reply line and the sending IP Message trace, platform logs Provider, code family
2 Do the SPF, DKIM and DMARC records resolve quickly from more than one resolver? dig against public resolvers and each authoritative server DNS hosting fault, temperror
3 Is SPF within 10 lookups and two void lookups? SPF checker, manual count permerror
4 Does the sending IP have a PTR record whose name resolves back to it? dig -x, then forward lookup Gmail 4.7.0 / 4.7.23
5 Does the MAIL FROM and header From domain have SOA and A or MX records? dig SOA Yahoo unresolvable-domain 451
6 Did volume change? New campaign, list import, IP or platform migration Platform statistics, client change log Rate limiting
7 What do reputation tools show? Google Postmaster Tools, Yahoo Complaint Feedback Loop Reputation, complaints
8 Any sign of a compromised account sending spam? Outbound queues, sign-in logs Abuse

For step 2, query a public resolver and each authoritative server:

dig +tries=1 +time=3 TXT _dmarc.example.com @8.8.8.8
dig +tries=1 +time=3 TXT example.com @ns1.example-dns.net

A timeout or SERVFAIL from one authoritative server but not another explains intermittent temperror results. DNS lookup fundamentals for MSPs covers resolvers and authoritative servers, and reverse DNS and email authentication covers step 4.

For step 7, Google's Postmaster Tools dashboards include a Delivery errors dashboard showing the percentage of authenticated messages "rejected or that temporarily failed", with reasons such as "Rate limit exceeded", "Sending IP has a low reputation" and "Bad or missing PTR record".

10

What do DMARC aggregate reports show about deferred mail?

Very little, by design. RFC 9990 describes report counts as "based on all messages received, even if their delivery is ultimately blocked", and does not say whether messages turned away with a 4xx reply during the SMTP session are counted. Do not use aggregate reports to measure deferrals.

What they do show is still useful for triage:

  • SPF and DKIM temperror or permerror results per source. A run of temperror points at DNS hosting; permerror points at a broken record.
  • Every source sending as the domain, with volumes. A sudden jump can explain rate limiting.

They do not show the reply code, the provider's reason text, complaint rates or reputation. DMARC aggregate reports explained shows how to read the XML. A multi-tenant platform such as DMARC AI for MSPs processes these reports per client domain, and its AI assistant can check a domain's live DNS records, which covers steps 2 and 3 of the triage table.

11

Frequently asked questions

Is a tempfail the same as a soft bounce?

Not quite. A tempfail is the 4xx reply itself, and your server keeps retrying. Many email platforms call a 4xx a "soft bounce" in their reports, but the message is usually still queued. It only becomes a true bounce, with a non-delivery report, when retries run out after the give-up time.

Should I resend a message that got a 4xx deferral?

No. Your server already retries automatically, and a manual resend adds volume, which can make rate limiting worse. Fix the cause the reply text names, then let the queue drain. If retries have already expired and the message bounced, resend it once the cause is fixed.

Can too many SPF lookups cause a deferral?

Not directly. Exceeding 10 DNS lookups is an SPF permerror, a permanent result that fails SPF for every message. Depending on the receiver and your DKIM and DMARC setup, that leads to rejection, spam placement or rate limiting such as Gmail's 421 4.7.27. A slow DNS host, by contrast, produces temperror.

Related articles

Related tools

Ready to Implement?

Get authenticated mail moving in minutes: start free, book a guided demo, or talk to the team about your stack.