WarningSMTP Error · Temporary (4.x.x)
421 4.7.0

Temporary deferral / rate limited

A 421 4.7.0 is a temporary failure — the server is deferring your mail, usually because it is rate-limiting you or throttling a sender it does not yet trust. Legitimate mail is normally retried and delivered.

Updated June 13, 2026

SMTP Exchange / Mail Log
> MAIL FROM:<you@yourdomain.com>> RCPT TO:<recipient@example.com>  421 4.7.0 Temporary deferral / rate limited
All guides

Is your domain affected?

Run a free check — we'll show you exactly what's misconfigured.

421 4.7.0 is a temporary SMTP reply meaning temporary deferral / rate limited. 4xx codes are temporary. 421 means "service not available, closing channel" and 4.7.0 indicates a policy-based throttle. Your mail server should automatically retry on a backoff schedule.

What 421 4.7.0 means

4xx codes are temporary. 421 means "service not available, closing channel" and 4.7.0 indicates a policy-based throttle. Your mail server should automatically retry on a backoff schedule.

ℹ️
This is a 4.x.x temporary failure — a correctly configured mail server retries on a backoff schedule, and the message frequently delivers on a later attempt.

Common causes

📨
#1

You're sending too fast for your reputation

Most common

New IPs or domains, or a sudden volume spike, get throttled until the receiver builds trust. This is the most common cause.

🔁
#2

The receiving server is temporarily overloaded

Common

Genuine temporary resource limits on the receiver's side; these clear on retry.

⚙️
#3

Greylisting

Common

Some servers defer the first attempt from an unknown sender on purpose and accept the retry.

How to fix 421 4.7.0

  1. 1

    Let your server retry — don't panic

    A properly configured mail server retries 4xx deferrals automatically. A single 421 4.7.0 that later delivers is not a problem.

  2. 2

    Warm up new IPs and domains gradually

    Ramp volume slowly over days/weeks so receivers build trust. Sending full volume from a cold IP guarantees throttling.

  3. 3

    Fix authentication and reputation if it persists

    Sustained 421s across recipients point to a reputation problem — verify SPF/DKIM/DMARC and check blacklists.

Confirm your domain is set up correctly

Most delivery failures — permanent or temporary — trace back to authentication or reputation. Run a free EmailHealth check to confirm SPF, DKIM, DMARC, blacklist status, and TLS are all healthy for your sending domain. If you send in volume, free daily monitoring will alert you before a small issue becomes a flood of bounces.

Stop this error from coming back

Most delivery problems start when a DNS record changes, a key is removed or a domain lands on a blocklist. EmailHealth checks your sending domains every day and sends one alert, by email, Slack or webhook, with the exact fix.

1 domain free. Sending from many domains (cold email, agencies, MSPs)? Early access covers 10.

Frequently asked questions

Check your domain for free

SPF, DKIM, DMARC, MX, blocklists and TLS in about 2 seconds. No account needed.

Run the check