SMTP Error 450

What is SMTP Error 450?

450 is a standard SMTP reply code defined in RFC 5321 §4.2.3 as:

450 Requested mail action not taken: mailbox unavailable (e.g., mailbox busy or temporarily blocked for policy reasons)

The critical detail is the first digit. Per RFC 5321 §4.2.1, a reply beginning with 4 is a Transient Negative Completion reply: "The command was not accepted, and the requested action did not occur. However, the error condition is temporary, and the action may be requested again." In other words, 450 is not a bounce. The receiving server has deferred your message, and a well-behaved sender is expected to queue it and retry later. This is what separates 450 from the permanent 550 (mailbox unavailable, do not retry).

A 450 is frequently paired with an RFC 3463 enhanced status code that narrows the cause. Per the RFC itself, 4.2.2 = mailbox full, 4.3.2 = system not accepting network messages, and 4.7.1 = delivery not authorized / policy hold. In practice, receivers also commonly reuse 4.2.0 ("other or undefined mailbox status") for greylisting and 4.2.1 ("mailbox disabled, not accepting messages") for rate limiting — for example, Gmail's own literal reply text is 450 4.2.1 ... receiving mail too quickly — though that specific reuse is a vendor convention layered on top of the RFC's definitions, not the RFC's own meaning. Always read the full text the server returns; the 3-digit code alone is intentionally generic.

What causes SMTP Error 450?

• Greylisting. Many servers reject the first delivery attempt from an unfamiliar IP/sender/recipient triplet with a 450 on purpose, expecting a legitimate server to retry. Spam bots usually don't retry; real mailers do. This is one of the most commonly cited causes.
• Rate limiting / throttling. You're sending too fast for the receiver's per-IP or per-recipient limits (often surfaced as 4.2.1).
• Temporarily over-quota or busy mailbox. The recipient's mailbox is full or locked during maintenance (4.2.2).
• Temporary policy or reputation hold. The receiver is deferring mail from your IP while it evaluates reputation, or is under load (4.7.1, 4.3.2).

Note: a 450 does not mean the address doesn't exist (that's a permanent 550/5.1.1) and it is not, by itself, evidence that your IP is permanently denylisted. Treating a transient 450 as a hard failure and dropping the message is a common — and incorrect — mistake.

How do I fix SMTP Error 450?

1. Retry with backoff first. Because 450 is transient, the correct response is to keep the message queued and retry. Most MTAs do this automatically over a multi-hour-to-multi-day window. For greylisting, a single retry a few minutes later typically succeeds. Do not delete the message or rewrite it on the first 450.
2. Read the enhanced code and any server text. A 4.2.1 points at rate limiting (slow down); 4.2.2 points at the recipient's quota (their problem, retry later); 4.7.1 points at a policy/reputation hold (authenticate and warm up).
3. Reduce send rate if you're being throttled. Spread volume out, respect per-recipient-domain concurrency limits, and ramp new sending IPs gradually (IP warm-up).
4. Authenticate so you bypass greylisting and policy holds. Publish and align SPF (RFC 7208), DKIM (RFC 6376), and DMARC (RFC 9989), which obsoletes the older RFC 7489 (with RFC 9990 covering aggregate reporting and RFC 9991 covering failure reporting). Authenticated, reputable senders are often whitelisted past greylisting entirely.
5. Watch out for IP rotation on ESPs. Large providers (SendGrid, Amazon SES, Mailgun) rotate outbound IPs. If a retry leaves from a different IP than the original, some greylisting implementations see a new triplet and defer again. Using a consistent/dedicated IP or a provider that handles greylisting retries internally avoids this loop.
6. Confirm it isn't actually persistent. If a destination returns 450 on every attempt for days, the message will eventually time out and bounce. At that point investigate reputation/denylisting with a tool such as MXToolbox Blacklist Check and contact the receiving domain's postmaster.