Blazalek.com

4.2.0SMTP 4.2.0: Recipient temporarily unavailable

4.2.0 reports a temporary, unspecified recipient-mailbox condition. Preserve the complete reply, retry with a limit, and do not infer quota, a rate limit, or a permanent address defect.

Category
Recipient mailbox
Class
Temporary failure
Retry
Controlled retry
Suppression
Check the full context

TL;DR

Generic temporary mailbox condition: use bounded retry and do not suppress from this code alone.

What this code means

X.2.0 is the mailbox-family catch-all. This class-4 code is published on exact Comcast 450 evidence, not an IANA-confirmed class assignment.

Provider examples

comcast example
smtp;450 4.2.0 <example@comcast.net> - Recipient temporarily unavailable

Technical meaning

The reply gives no more specific mailbox condition.

Delivery status

Class 4 may clear and does not establish an invalid recipient.

Class
Temporary failure
Retry
Controlled retry
Suppression
Check the full context

Retry decision

Retry with backoff, jitter, idempotency, and a limit; stop on success, permanent result, or exhaustion.

Suppression decision

Do not suppress from 4.2.0 alone; require independent permanent evidence or policy.

Common causes

  • A provider-side temporary hold or generic recipient deferral.

Diagnostic steps

  1. Retain recipient, time, and full reply; do not choose a cause from these digits.

Actions by owner

Sender

  • Retry with a limit and share the exact reply if it persists.

Recipient

  • Check for a provider notice without assuming the code names one.

Recipient administrator

  • Check quota, suspension, or policy holds and confirm with the provider.

Sources

These sources define what this enhanced status code means, mainly through the IANA registry and related RFCs. When provider examples appear on the page, they come from that provider's published documentation. Follow the links to read the original wording in context.

Last verified:

Found an error or inaccuracy? Report a correction.

Point out the part of this page that should be checked. Every report is reviewed manually.

Type of problem

Describe the issue and, if useful, suggest corrected wording.

For a factual report, include a public source when possible.

You can submit anonymously. A reply is not guaranteed.

Do not paste full bounce messages, headers, email addresses, Message-IDs, tokens, or other personal data. Redact evidence before sending.

Sending a correction shares the information you enter with Formspree so I can review and improve this page. Read the privacy notice.

Guide

Incidents

Wojtek Blazalek

Email deliverability expert

Stuck on this error code? I help teams identify rejection causes and fix authentication and reputation, so email reaches the inbox.

Hands-on deliverability work for teams that send at scale.