Article
SMTP 450 Requested Mail Action Not Taken: What It Means and How to Fix It
By Unlimited Verifier Team ·

Summary
SMTP error 450 is a temporary 4xx rejection meaning the receiving server won't accept your message right now, often due to a busy mailbox, rate limiting, or greylisting. It is not a permanent verdict on the address, so senders should retry and only act if the 450 persists for several days.SMTP error 450, "Requested mail action not taken: mailbox unavailable," is a temporary (4xx) rejection meaning the receiving server won't accept your message right now, usually because the mailbox is busy, rate-limited or greylisting you. It is not a verdict on the address, so the sending server should retry, and only a 450 that persists for days is worth acting on.
Quick answer
- What it means: A 450 is a 4xx "try again later" reply. RFC 5321 defines it as a mailbox that is busy or temporarily blocked for policy reasons.
- Is it a bounce? Not yet. It's a deferral, which most platforms classify as a soft bounce. It becomes a failed delivery only if retries keep failing until the sender gives up.
- What to do: Group your 450s by domain and text before acting. A cluster at one provider usually means throttling, so slow the send. Scattered addresses that keep failing usually mean dead mailboxes, so verify them and suppress the bad ones.
- Threshold to act on: Treat an address that still returns a 450 after about five days of retries as unreachable until verification says otherwise.
What does "Requested mail action not taken" actually mean?
The code is defined in RFC 5321, the core SMTP specification. The first digit, 4, marks a transient negative completion, so the sender should try again. The second digit, 5, places it in the mail-system category, and the third digit, 0, is unspecified. A 5xx reply from the same server would mean it is refusing permanently.
The word that matters is mailbox. The receiving server accepted your connection, understood who the recipient was, and chose not to take the message right now. It has not said the address is invalid.
Most 450 replies also carry an enhanced status code, defined in RFC 3463. The ones you will see most often are:
- 4.2.1: Mailbox disabled, not accepting messages.
- 4.2.2: Mailbox full.
- 4.7.1: Delivery not authorized, message refused. This is used for policy decisions.
Providers also add their own wording after the code, and that text often tells you more than the number. You'll usually find the full line in the bounce report your ESP sends back, or in the NDR that arrives from the mailer-daemon. If you're confused by those messages, our explainer on why you keep getting mailer-daemon bounce messages walks through them. If your recipients sit on Microsoft 365, the Office 365 NDR bounce codes list maps Microsoft's wording to its meanings.
Bottom line: A 450 means "not now, and not for a permanent reason." The text after the code tells you which kind of "not now" it is.
Why do mail servers return a 450?
A 450 usually comes from one of five causes. Each looks different in your logs and needs a different response.
| Cause | What it looks like | Can you influence it? | Typical fix |
|---|---|---|---|
| Greylisting | First attempt from a new sender–IP pair is deferred; a retry minutes or hours later succeeds | No, and you don't need to | Let the retry run |
| Rate limiting | Many 450s to one provider in a short window, often with wording about receiving too much mail | Yes | Lower concurrency for that domain and spread the send over hours |
| Reputation or policy hold | 450 or 4.7.x across many domains, growing day over day | Yes, but slowly | Check blocklists and reputation data, then reduce volume and fix list quality |
| Disabled mailbox | One address, deferred for days, sometimes with 4.2.1 | Only by removing the address | Verify, then suppress if invalid |
| Full or abandoned mailbox | One address, 450 or 452 on every send | Only by removing the address | Verify, then suppress |
Greylisting deserves special attention. Many receiving systems defer the first delivery from an unfamiliar sender and IP combination on purpose. Legitimate mail servers retry, and many bulk spam tools don't. A first-attempt 450 from a greylisting server is therefore often a sign that your mail is behaving normally.
The first hour of a campaign can also mislead you. Public ESP documentation generally reports deferred events separately from final bounces. A campaign that looks clean at hour one can look quite different on day five, once the retries have run.
Bottom line: Most 450s either clear by themselves or come from how fast you send. A single address that keeps returning 450 is the pattern that points to the list.
Is a 450 a soft bounce or a hard bounce?
A 450 is a soft bounce, also called a transient failure. A hard bounce is a permanent 5xx failure such as 550 5.1.1 (user unknown). The difference determines what you do next.
| 450 (transient) | 550 5.1.1 (permanent) | |
|---|---|---|
| SMTP class | 4xx, temporary | 5xx, permanent |
| Sender retries? | Yes, for several days | No |
| Typical ESP classification | Soft bounce or deferral | Hard bounce |
| What it says | "Try later" | "This address does not exist" |
| Correct response | Throttle or wait; verify if it persists | Remove and suppress immediately |
The grey area is the handoff between the two. When retries run out, the sender generates a non-delivery report, and many platforms then count the address as a bounce. Platforms don't publish a common rule for how many soft bounces trigger suppression, so check your own ESP's documentation.
Our recommendation is to use three soft-bounce failures across separate sends, spanning at least five days, as the trigger to verify and suppress. Three attempts is a common platform pattern, and five days covers the retry window that RFC 5321 suggests (see the section on retry windows below). If you want to see how these soft-bounce causes sit alongside the rest, our common soft bounce reasons list covers the full set.
Bottom line: Treat a 450 as a soft bounce that needs a pattern check. Escalate to suppression only when it repeats across days, not just sends.
How do you tell a harmless 450 from a real list problem?
Use the pattern, not the code alone. Five patterns cover most cases.
| Pattern | Likely cause | Action |
|---|---|---|
| One address, 450 once, delivered on retry | Greylisting or a momentarily busy mailbox | None |
| Cluster at one provider in the same hour, rate-limit wording | Throttling by that provider | Reduce concurrency for that domain; spread the send over hours |
| Scattered addresses across many domains, 4.7.x policy wording, rising day over day | Sender reputation or a blocklist | Check your sending IP and domain against blocklists, review Google Postmaster Tools, and pause volume until the cause is clear |
| Same address deferring on every send for days | Full, disabled or abandoned mailbox | Verify the address; suppress if invalid |
| Spike concentrated in an old or recently imported list | Dead or recycled addresses combined with throttling | Verify the list before resending anything |
A common mistake is treating a throttling cluster as a list problem. Cleaning the list won't fix a provider that is only slowing you down, and you'll lose valid contacts in the process. The reverse mistake is just as costly: throttling a list full of dead addresses won't make them deliverable.
Blocklist checks deserve their own step. Unlimited Verifier offers a free domain blacklist checker, which is a quick way to see whether your sending domain is listed before you assume the problem is your data.
Bottom line: Throttling is a sending-speed problem and needs a sending fix. A single address that keeps deferring is a list problem and needs verification.
Does a 450 hurt your sender reputation?
A deferral by itself is not a complaint signal, and most 450s recover on retry without lasting damage. What hurts reputation is repeatedly mailing dead addresses and generating spam complaints.
Google's sender guidelines name a user-reported spam rate of 0.10% as the level to stay under and 0.30% as the line not to cross. A large clump of deferrals doesn't change that number directly, but if you respond by resending to the same dead addresses, you add bounces and complaints that do.
Bottom line: A 450 is a reason to slow down and check, not a reputation penalty. The damage comes from what you do next.
What should you do the moment you see a 450?
Work through these steps in order. They take less time than the campaign report you're tempted to act on first.
- Don't resend the failed batch immediately. Each retry joins the same throttled queue and can deepen the deferral. Let the sender's built-in retry schedule run.
- Pull deferral events, not just the bounce list. Filter for 4xx codes, including 450. Record the time, the recipient domain and the enhanced code.
- Group the 450s by domain and by text. Use the pattern table above to decide which cluster you're looking at.
- Fix the sending side first. For a throttling cluster, reduce concurrency to that domain. Confirm your SPF, DKIM and DMARC records are in place, because authentication affects how receivers treat your mail.
- Set a persistence rule. An address still returning 450 after about five days is no longer "busy." It moves to verification.
- Verify the persistent addresses using the tutorial below.
- Act on the results. Suppress Invalid addresses, hold back the ones you can't confirm, and resend Valid ones in a capped batch.
- Record the counts. Save the number deferred, the number recovered on retry and the number verified. You'll need them if the problem returns or if you have to explain it to your ESP.
Bottom line: Slow down first, then diagnose, then clean. Reversing that order is how teams end up deleting good contacts.
How do you clean a bulk list of persistent 450 addresses?
This tutorial covers the verification step. You'll need the addresses that stayed in 450 status after retries. Choosing a tool is a separate decision, and our guide on how to choose an email verifier and roundup of best email verification tools cover the comparison.
Verification checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. One caveat: a verifier's own mailbox check can meet a temporary response from the receiving server. Treat any result you can't confirm as unproven, whichever bucket a tool puts it in.
- Export the persistent addresses from your ESP as a CSV. Include one email column. Add a column for the last deferral code if your ESP provides it. Keep the file under 10MB.
- Create an account. Sign up for a free account. The Free plan takes lists of up to 150 emails, up to 25 lists a month, with 750 deep verifications a month. Results are kept for 24 hours, so download them the same day. The Pro plan ($29 a month, or $25 a month billed annually) takes lists of up to 25,000 emails, with 25,000 deep verifications a month, API access and results kept for 30 days.
- Upload the file. Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. On Pro, split any file with more than 25,000 rows into separate lists first.
- Choose your verification depth. Standard verification is unlimited on every plan, including Free. Deep verification counts against your monthly allowance, so save it for addresses where the decision matters most, such as high-value contacts or addresses that have deferred repeatedly.
- Read the three buckets.
- Valid: the mailbox was confirmed. Safe for a capped resend.
- Invalid: remove and suppress permanently.
- Risky: the address needs a decision before you send. Unlimited Verifier flags catch-all domains (which accept every address, so a mailbox can't be confirmed), disposable addresses and role accounts such as info@. Hold these back. For catch-all handling, see catch-all email verification.
- Spot-check the edge cases. For a single address you're unsure about, use the free email checker.
- Export the results as CSV, Excel or JSON. Save the summary counts for your records.
- Act and re-import. Add Invalid addresses to your ESP's suppression list. Create a segment of Valid contacts for the resend. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so the re-import is manual: upload the Valid file to your ESP. Teams that want to automate this can use the email verification API, which supports single-email checks and bulk batches of up to 10,000 emails per request. API access is on Pro, with 100,000 API emails a month. For automation patterns, see email verification API and automation. To catch these addresses at signup rather than after a campaign, look at real-time email validation.
Bottom line: Verification turns "this address deferred" into a result you can act on. Only the Invalid and held-back groups need a decision from you.
How much does verifying 450 addresses cost?
Costs depend on how many deep checks you run. Standard checks are unlimited on every plan. The email verification pricing of the Unlimited Verifier plans gives three useful numbers:
- Pro, monthly: $29 ÷ 25 thousand deep checks = $1.16 per 1,000 deep verifications if you use the full allowance.
- Pro, annual: $25 ÷ 25 thousand = $1.00 per 1,000 deep verifications at full use.
- Free: $0, with 750 deep verifications a month. For a few hundred persistent addresses, that is enough.
Those figures assume full use of the deep allowance. A small clean-up often costs nothing on the Free plan. The bigger cost is the valid contacts you'd lose by deleting on the first deferral, which the worked example below shows.
Bottom line: For most 450 clean-ups, the tool cost is zero to a few dollars. The expensive mistake is deleting good contacts.
What does a real 450 cleanup look like in numbers?
This example is illustrative. The send and the verification results are hypothetical, but the plan limits and the arithmetic are real. It uses a SaaS company, the kind of team covered in email verification for ecommerce and SaaS.
The send: The company sends a product update to 40,000 contacts. The ESP reports 1,200 deferrals with 450 codes.
1,200 ÷ 40,000 = 3.0% deferral rate
Breakdown: The 1,200 split into two patterns:
- 880 deferrals at one large mailbox provider, with rate-limit wording.
- 320 deferrals scattered across 140 domains, with 4.2.1 and 4.2.2 codes.
Day 0: The team halves concurrency for the affected provider and changes no list. Deleting the 880 would have removed 2.2% of the list (880 ÷ 40,000) with no evidence those addresses were bad.
Day 1: All 880 throttled contacts are delivered on retry.
Days 1–5: Of the 320 scattered deferrals, 210 deliver on retry. That leaves 110.
210 ÷ 320 = 65.6% recovered; 110 still deferring
Day 5: The 110 persistent addresses are exported and verified.
110 ÷ 40,000 = 0.28% persistent deferral rate
Verification results:
| Bucket | Count | Action |
|---|---|---|
| Valid | 25 | Resend in a capped batch to the most engaged |
| Risky | 21 | Hold back; test later if needed |
| Invalid | 64 | Suppress permanently |
Check: 25 + 21 + 64 = 110.
Plan fit:
- The 110-address clean-up fits on Free. It's under the 150-email list limit. Running deep checks on all 110 uses 110 of the 750 monthly deep verifications.
- The full 40,000 list does not fit on Free. Free allows 25 lists of up to 150 emails a month, which caps out at 3,750 emails. The full list needs Pro, split into two lists (25,000 + 15,000).
- On Pro, the same 110 addresses use 110 of 25,000 monthly deep verifications and fall within the $29 monthly plan.
Outcome: 64 addresses are suppressed, which is 0.16% of the list (64 ÷ 40,000). The 25 Valid addresses go out in a capped batch. The 21 Risky addresses wait until the Valid group's bounce rate has stayed below 1% for a full send cycle.
Bottom line: Only 0.16% of the list was removed, and almost none of the 3.0% deferral was caused by bad data.
How do 450 and other temporary codes compare?
450 sits in a family of 4xx replies. The meanings below come from RFC 5321, and the typical triggers reflect common practice.
| Code | RFC 5321 meaning (short form) | Typical trigger | First move |
|---|---|---|---|
| 421 | Service not available, closing transmission channel | Server overloaded or throttling the connection | Wait; if it repeats, see 421 4.7.0 try again later |
| 450 | Mailbox unavailable: busy or temporarily blocked for policy | Greylisting, rate limits, policy holds, busy mailbox | Triage by pattern |
| 451 | Requested action aborted: local error in processing | A fault on the recipient's server | Usually clears on retry; escalate only if persistent |
| 452 | Insufficient system storage | Mailbox or server out of space | Persistent 452 on one address points to a full mailbox; verify |
For how 4xx and 5xx differ at the protocol level, see 4xx vs 5xx SMTP errors. For the broader set of codes and fixes, the most common email bounce codes and how to fix them guide is a good companion.
Bottom line: The number tells you the category. The text and the pattern tell you the fix.
How long does a 450 keep retrying before it becomes a bounce?
RFC 5321 suggests that sending servers retry at intervals of at least 30 minutes and keep trying for at least four days. Implementations differ, so give the RFC figure a little weight and check your ESP's own rules. Many mail server defaults run for about five days.
Our recommendation is to use five days as your persistence threshold. It covers the RFC window, so an address still failing at day five has had a fair chance to recover. If your ESP reports a final bounce earlier, the five-day rule still applies to your decision: verify the address before you resend it.
Bottom line: Judge persistence by days, not by how the ESP labels the event.
What are the most common mistakes with 450 errors?
- Deleting addresses on the first deferral. Most 450s clear on retry. In the worked example, the throttled cluster was 2.2% of the list, and deleting it would have removed valid contacts for no reason.
- Resending the batch right away. Immediate retries join the same throttled queue and can extend the deferral.
- Cleaning the list to fix a rate limit. Throttling needs slower sending. List cleaning addresses a different problem.
- Judging the campaign by hour one. Deferrals and retries arrive in waves. Wait for the retry window before drawing conclusions.
- Trusting an unconfirmed verification result. A verifier's mailbox check can meet a temporary response. Treat unconfirmed results as unproven, and don't send to them at full volume.
- Assuming Valid means deliverable today. A mailbox can be valid and still full on a given day (452). Keep sends capped even for Valid contacts.
- Dropping catch-all addresses without a test. A catch-all result doesn't confirm a mailbox. Test with a small, engaged group before deciding.
- Ignoring the enhanced code. 4.7.1 (policy) and 4.2.2 (mailbox full) need different responses. Read the full line before acting.
- Treating verification as proof of consent. A Valid address is a deliverable address, not an opted-in one. Verification supports email verification compliance and hygiene but doesn't replace permission to mail.
- Mixing up 450 and 550 in support tickets. Quote the exact code and text. A 550 is permanent, and a 450 is not. Describing one as the other sends your ESP's support team down the wrong path.
Bottom line: Most 450 mistakes come from acting too early, acting on the wrong category, or treating an unconfirmed result as proof.
How we compared (and limitations)
This article is based on public documentation: the text of RFC 5321 and RFC 3463, Google's sender guidelines, Yahoo's sender requirements, and the publicly available documentation of major ESPs. We have not run controlled tests against receiving servers or ESP review teams.
Three limitations matter:
- Wording varies. Providers change their 4xx text without notice, so match your logs against the patterns above rather than exact strings.
- Retry windows vary. The RFC suggestion and ESP practice differ. Use the five-day threshold as a planning number and check your ESP's rules.
- Worked-example figures are illustrative. The arithmetic is real. The send, the deferral split and the verification results are hypothetical.
Unlimited Verifier's 99.5% accuracy figure for deep verification is the company's stated figure, not an independent benchmark. Its verification engine is open source on GitHub, so you can check for yourself how it handles temporary responses.
For the broader picture of codes and fixes, start with our pillar guide to email bounce codes. For ongoing hygiene after the cleanup, see email list maintenance best practices.
Bottom line: Use the RFC codes as the framework, your own logs as the evidence, and verification as the tiebreaker.
450 causes and responses
| Cause | What it looks like | Typical fix |
|---|---|---|
| Greylisting | First attempt deferred, retry succeeds | Let the retry run |
| Rate limiting | Many 450s to one provider in a short window | Lower concurrency for that domain |
| Reputation or policy hold | 450 or 4.7.x across many domains | Review authentication and list hygiene |
| Mailbox full or disabled | 4.2.2 or 4.2.1 that persists | Verify address and suppress if it stays unreachable |
Frequently asked questions
Is SMTP 450 a hard bounce?
No. A 450 is a temporary 4xx deferral, so it is typically treated as a soft bounce. The sending server keeps retrying, and the message only fails if retries keep getting 450 responses until the sender gives up.
How long should I retry after a 450 error?
Most sending servers retry for several days using increasing delays. If an address still returns a 450 after about five days of retries, treat it as unreachable until you verify it.
What causes a 450 requested mail action not taken error?
Common causes include greylisting of new sender and IP pairs, rate limiting from a provider receiving too much mail, reputation or policy holds, a full or disabled mailbox, and temporary server problems.
Does a 450 mean the email address doesn't exist?
Not usually. A nonexistent address normally returns a permanent 5xx code such as 550. A 450 signals a temporary condition, so the mailbox may exist but be busy or throttled.
What is the difference between 450 and 550 SMTP errors?
A 450 is a temporary 4xx reply telling the sender to try again later. A 550 is a permanent 5xx reply indicating the mailbox is unavailable or refused, and the sender should stop retrying that address.
How do I fix repeated 450 errors to one domain?
Group the 450s by receiving domain and error text. If they cluster at one provider, reduce concurrency for that domain and spread sending over several hours. Check your sending reputation and authentication records too.
Can greylisting cause a 450 error?
Yes. Greylisting defers the first delivery attempt from an unknown sender and IP pair. A retry a few minutes or hours later usually succeeds, so no action is needed beyond letting the retry run.
Should I remove addresses that return 450?
Not immediately. Keep them in retry queues and monitor them. Suppress or verify only those that keep returning 450 or 4.2.1 for an extended period, since those codes can signal a disabled mailbox.
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 standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
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.