4.x.x — SMTP Temporary Failure Codes
Class 4 enhanced status codes report a temporary failure for the current attempt. A controlled retry can be appropriate after you identify the exact condition, timing, limits, route, and provider guidance.
A leading 4 is a soft failure: the condition may clear on its own. Retry with backoff rather than adding the recipient to a suppression list, and confirm the exact reason from the complete SMTP response before changing send behavior.
A leading 4 means the reported attempt did not complete and the condition may change, but it does not promise that repeating the same send will work. Read the full response and detailed code to decide whether to use bounded backoff, reduce sending pressure, repair a route or message condition, or escalate with evidence; do not infer that the recipient is invalid from class 4 alone.
Choose the next check
- Capture the exact response and timingKeep the basic reply, enhanced code, provider text, destination, and attempt time; the generic class-4 label is not enough to select a retry policy.
- Check recipient and mailbox availabilityA temporary mailbox or recipient condition may call for waiting or rate adjustment, not a permanent recipient-state change.
- Check system, DNS, and routing conditionsWhen the response points to capacity, name resolution, connectivity, or routing, diagnose the relevant path before retrying at scale.
- Check policy, authentication, and rate limitsProvider policy or anti-abuse deferrals need a specific repair or sending adjustment; more retries without that change can prolong the problem.
Common mistakes
- Retrying every class-4 response forever without a bounded backoff policy, response-specific limit, or escalation threshold.
- Adding a recipient to suppression based on a temporary code without checking the exact response and recipient history.
- Treating a provider rate-limit or authentication deferral as a generic timing issue instead of correcting the identified sender-side condition.
Codes in this category
This inventory contains only reviewed codes assigned to this subject. Open a code to see its evidence, diagnostic steps and owner-specific actions.
- 4.0.0Other undefined temporary statusCode 4.0.0 is a general temporary failure: only class 4 is known, with no more specific status. The message may be retried in a controlled way.CategoryOther and undefinedRecommended actionControlled retry
- 4.1.1Temporary destination mailbox address problemThe receiving system did not find the specified mailbox during this attempt. Because the code begins with 4, this is a temporary failure: delivery may be retried in a controlled way, but the code alone does not yet establish that the address is permanently invalid.CategoryAddressingRecommended actionControlled retry
- 4.1.8Temporary sender system address problemThis attempt reported a problem with the system identified by the sender address. Because the code begins with 4, it is a temporary failure: delivery may be retried in a controlled way, but the sender address and system configuration should be checked first.CategoryAddressingRecommended actionControlled retry
- 4.2.0Recipient mailbox temporarily unavailable (other/undefined mailbox status)The receiving system reports that the mailbox exists but is temporarily unable to accept the message for an unspecified reason. The code belongs to the temporary class: delivery may succeed on a later attempt.CategoryRecipient mailboxRecommended actionControlled retry
- 4.2.1Recipient mailbox temporarily not accepting messages (receiving-rate limit)The receiving system reports that the mailbox exists but is not currently accepting messages, most often because the recipient is receiving mail faster than the system allows. The code belongs to the temporary class: the condition is expected to clear, so delivery may be retried in a controlled way.CategoryRecipient mailboxRecommended actionControlled retry
- 4.2.2Recipient mailbox temporarily over its storage quotaThe receiving system reports that the mailbox is currently over its storage limit and is not accepting messages. The code belongs to the temporary class: the recipient may free up space, so delivery may be retried in a controlled way.CategoryRecipient mailboxRecommended actionControlled retry
- 4.2.4Temporary mailing-list expansion problemThe receiving system recognized the destination as a mailing list but could not expand it to recipients during this attempt. The code belongs to the temporary class, so delivery may be retried in a controlled way.CategoryRecipient mailboxRecommended actionControlled retry
- 4.3.0Other or undefined temporary mail-system statusThe destination system exists and normally accepts mail, but a general problem in that system prevented delivery during this attempt. The leading digit 4 denotes a temporary failure, so delivery may be retried in a controlled way.CategoryMail systemRecommended actionControlled retry
- 4.3.1Temporarily full mail systemThe mail system exceeded its available storage during this attempt. This is a system-wide resource problem, so an individual recipient may be unable to free space on their own. Because the code begins with 4, delivery may be retried in a controlled way.CategoryMail systemRecommended actionControlled retry
- 4.3.2System temporarily not accepting network messagesThe host on which the recipient's mailbox resides is not currently accepting messages. Because the code begins with 4, this is a temporary failure and delivery may be retried in a controlled way.CategoryMail systemRecommended actionControlled retry
- 4.4.0Temporary failure for an unspecified network or routing reason (other/undefined network status)The receiving system reports a temporary failure using the generic "other or undefined network or routing status" code: some network-layer or routing/replication condition prevented delivery at this attempt, but the response does not identify one of the more specific network conditions this catalog also tracks (no answer from host, bad connection, directory server failure, mail system congestion, a routing loop, or delivery-time expiry). The code belongs to the temporary class: whatever condition triggered it may clear, so delivery may be retried in a controlled way.CategoryNetwork, DNS and routingRecommended actionControlled retry
- 4.4.1No answer from remote hostAn outbound connection attempt received no answer from the remote system. The standard indicates that the system may have been busy or unable to accept a connection. The code belongs to the temporary class, so delivery may be retried in a controlled way.CategoryNetwork, DNS and routingRecommended actionControlled retry
- 4.4.2Bad connectionAn outbound connection was established, but the message transaction could not be completed over it. The standard points to a timeout or inadequate connection quality. The code belongs to the temporary class, so delivery may be retried in a controlled way.CategoryNetwork, DNS and routingRecommended actionControlled retry
- 4.4.3Directory server failureThe network system could not forward the message because a directory server was unavailable. Inability to connect to an Internet DNS server is one standards example, but the code alone does not prove that the problem involved DNS. The code belongs to the temporary class, so delivery may be retried in a controlled way.CategoryNetwork, DNS and routingRecommended actionControlled retry
- 4.4.5Mail system congestionA mail system could not deliver the message because it was congested. The code does not identify which system or party is responsible for that condition. It belongs to the temporary class, so delivery may be retried in a controlled way.CategoryNetwork, DNS and routingRecommended actionControlled retry
- 4.4.6Routing loop detected between mail systemsThe sending or an intermediate mail system reports that this message was forwarded from system to system too many times without reaching its destination — a routing loop. The code belongs to the temporary class: once whichever forwarding rule or routing table is causing the loop gets fixed, delivery may succeed, so retrying in a controlled way is appropriate.CategoryNetwork, DNS and routingRecommended actionControlled retry
- 4.5.0Other or undefined temporary protocol statusA problem occurred with the protocol needed to pass the message to the next system, but no other detail code described it adequately. The leading digit 4 makes this a temporary result, so delivery may be retried in a controlled way.CategoryDelivery protocolRecommended actionControlled retry
- 4.5.1Temporarily invalid protocol commandA mail system rejected a protocol command because it was issued out of sequence or was unsupported. The leading digit 4 classifies this concrete result as temporary, so delivery may be retried in a controlled way after the command context is checked.CategoryDelivery protocolRecommended actionControlled retry
- 4.5.3Too many recipientsOne message specified more recipients than the protocol could handle in that attempt. The code belongs to the temporary class; normally, the remaining recipients should be separated and delivery to them retried in a controlled way.CategoryDelivery protocolRecommended actionControlled retry
- 4.5.4Temporarily invalid command argumentsA mail system recognized the command but rejected its arguments as invalid. The leading digit 4 classifies this concrete result as temporary, so delivery may be retried in a controlled way after the arguments are checked and, when necessary, corrected.CategoryDelivery protocolRecommended actionControlled retry
- 4.7.0Other or undefined temporary security statusThe message was returned because of a security-related problem, but the response does not describe it more precisely. The leading digit 4 denotes a temporary failure, so delivery may be retried in a controlled way.CategorySecurity, authentication and policyRecommended actionControlled retry
- 4.7.1Delivery not authorized, message temporarily refusedThe system refused the current attempt because the sender was not authorized to send to the destination. The decision may result from per-host or per-recipient filtering. The leading digit 4 denotes a temporary failure, so delivery may be retried in a controlled way.CategorySecurity, authentication and policyRecommended actionControlled retry
- 4.7.3Receiving domain's inbound queue temporarily over its rate quota (Outlook.com)The receiving system reports that the destination domain's incoming mail queue is currently receiving mail faster than its allotted rate quota and is not accepting messages at this time. The code belongs to the temporary class: the condition is tied to inbound volume, not to this message or this sender, so delivery may be retried once the queue has room again.CategorySecurity, authentication and policyRecommended actionControlled retry
- 4.7.12Authentication mechanism transition requiredThe server replied to the AUTH command that the user must first transition to the selected authentication mechanism. The leading digit 4 denotes a temporary failure, so a controlled attempt may be made after the required transition is completed safely.CategorySecurity, authentication and policyRecommended actionControlled retry
- 4.7.15Priority level is too lowThe receiving SMTP server did not accept the message because the specified priority level was below the lowest level the server currently accepts. The leading digit 4 denotes a temporary failure, so a controlled retry is appropriate.CategorySecurity, authentication and policyRecommended actionControlled retry
- 4.7.16Message too big for the specified priorityThe server temporarily rejected the message because it is too big for the specified priority. A controlled retry may be made after the condition clears.CategorySecurity, authentication and policyRecommended actionControlled retry
- 4.7.24SPF validation errorAn error occurred while SPF was evaluated for the arriving message, so the current attempt ended in a temporary failure. A controlled retry is appropriate, not unlimited retries.CategorySecurity, authentication and policyRecommended actionControlled retry
- 4.7.26Mail rate-limited for missing SPF/DKIM authentication (Gmail)The receiving system reports that mail from this sender is being rate-limited because it arrived without a passing SPF or DKIM authentication result. The code belongs to the temporary class: once the sender's authentication is corrected, delivery may be retried in a controlled way.CategorySecurity, authentication and policyRecommended actionControlled retry
- 4.7.28Sender IP temporarily rate-limited for unsolicited mail (Gmail)The receiving system reports that mail from this sending IP address is being rate-limited because Gmail judged an unusual portion of that traffic to be unsolicited. The code belongs to the temporary class: sending behavior and reputation may improve, so delivery may be retried in a controlled way.CategorySecurity, authentication and policyRecommended actionControlled retry
Related resources
Guide
- Sending Reliability
Retry vs suppress for temporary 4xx failures.
- Deliverability
Inbox placement and bounce context for deferred mail.

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.
