Blazalek.com

4.3.2SMTP 4.3.2: Mail system temporarily not accepting messages

The host holding the recipient mailbox is not accepting network messages right now. Keep any provider subcode, retry with limits, and investigate repeated host-level results without declaring the recipient permanently invalid.

Category
Mail system
Class
Temporary failure
Retry
Controlled retry
Suppression
Check the full context

TL;DR

The recipient host is temporarily refusing messages. Retry with limits; do not suppress until independent permanent evidence appears.

What this code means

X.3.2 means the mailbox host is not accepting messages. 4.3.2 is temporary and can cover shutdown, load, or maintenance.

Provider examples

Microsoft / Outlook example
432 4.3.2 STOREDRV.Deliver; recipient thread limit exceeded
Microsoft / Outlook example
421 4.3.2 The maximum number of concurrent connections per resource forest has exceeded a limit, closing transmission channel. example.com. PRX8 [example.com]
Outlook.com consumer example
421 4.3.2 Service not available [outlook.com]
Outlook.com consumer example
451 4.3.2 Temporary server error. Please try again later ATTR17 [outlook.com]
Yahoo / AOL example
smtp;451 4.3.2 Internal server error

Technical meaning

The full response may narrow the cause; the generic code alone cannot identify the host condition.

Delivery status

Class 4 permits controlled retry and does not establish permanent host unavailability.

Class
Temporary failure
Retry
Controlled retry
Suppression
Check the full context

Retry decision

Check suppression, then retry with idempotency, backoff, jitter, and a time or attempt limit.

Suppression decision

Do not suppress on 4.3.2 alone; use independent permanent evidence or policy.

Common causes

  • Host shutdown, excessive load, or maintenance.

Diagnostic steps

  1. Retain host, time, full response, and subcode; ask the administrator or provider to inspect state and load.

Actions by owner

Sender administrator

  • Group results by host and time, and stop retrying after the configured limit.

Recipient administrator

  • Clear confirmed host conditions and verify message acceptance.

Provider

  • Inspect availability, load, and response-specific limits, preserving code and subcode.

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.