WarningSMTP Error · Temporary (4.x.x)
450 4.2.1

Mailbox unavailable / temporarily blocked

A 450 4.2.1 is a temporary failure meaning the recipient's mailbox is currently unavailable — disabled, busy, or deliberately deferring you. Retry usually succeeds.

Updated June 13, 2026

SMTP Exchange / Mail Log
> MAIL FROM:<you@yourdomain.com>> RCPT TO:<recipient@example.com>  450 4.2.1 Mailbox unavailable / temporarily blocked
All guides

Is your domain affected?

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

450 4.2.1 is a temporary SMTP reply meaning mailbox unavailable / temporarily blocked. 4.2.1 is "mailbox disabled / not accepting messages" but as a 4xx it's temporary. Often it's a reputation-based defer (the receiver throttling an untrusted sender) rather than a truly disabled mailbox.

What 450 4.2.1 means

4.2.1 is "mailbox disabled / not accepting messages" but as a 4xx it's temporary. Often it's a reputation-based defer (the receiver throttling an untrusted sender) rather than a truly disabled mailbox.

ℹ️
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

Reputation-based throttling

Most common

Gmail and others return 450 4.2.1 to slow down senders they don't yet trust, expecting legitimate mail to retry. Most common cause today.

🔁
#2

The mailbox is temporarily disabled or locked

Common

The account may be suspended, frozen, or undergoing maintenance on the recipient side.

⚙️
#3

The recipient server is deferring during high load

Less common

Temporary resource pressure causes a soft rejection that clears on retry.

How to fix 450 4.2.1

  1. 1

    Let it retry

    As a 4xx, your server retries automatically. Mail that later delivers needs no action.

  2. 2

    Improve reputation if 450 4.2.1 is widespread

    Persistent deferrals across many recipients mean a reputation problem — warm up sending, clean your list, and verify authentication.

  3. 3

    Check blacklists and authentication

    Run a free EmailHealth check to confirm you're not blacklisted and that SPF, DKIM, and DMARC pass.

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