Blazalek.com

4.0.0SMTP 4.0.0: Undefined temporary delivery status

Only the temporary failure class is known: 4.0.0 gives no finer reason for the failed attempt, so preserve the full response and retry through a bounded queue rather than treating the address as invalid.

Category
Other and undefined
Class
Temporary failure
Retry
Controlled retry
Suppression
Check the full context

TL;DR

A generic temporary failure has no stated cause. Retry with backoff and an attempt limit; do not suppress from 4.0.0 alone.

What this code means

4.0.0 is the class-4 form of X.0.0, the undefined enhanced-status pattern. It reports a temporary result without identifying a mailbox, network, policy, or content cause.

Technical meaning

X.0.0 is used when only the result class is known; 4.0.0 therefore denotes temporary failure.

Delivery status

Class 4 means this attempt may succeed later. It does not prove an invalid recipient or a permanent block.

Class
Temporary failure
Retry
Controlled retry
Suppression
Check the full context

Retry decision

Use idempotent retries with exponential backoff, jitter, and a time or attempt limit. Stop on success, a permanent result, or exhaustion of that limit.

Suppression decision

Do not suppress an address from 4.0.0 alone. Decide only from the full response history, an independent permanent signal, and applicable policy.

Common causes

  • The receiver returned a temporary failure without a more specific enhanced code, or processing normalized richer detail to 4.0.0.

Diagnostic steps

  1. Retain the raw response, SMTP stage, and attempt time; determine whether a more specific status was lost before making another bounded attempt.

Actions by owner

Sender administrator

  • Place the message in a bounded idempotent retry queue and retain the raw response.

Provider

  • Preserve any available detailed status instead of replacing it with generic 4.0.0.

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

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.