What this code means
The 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.
Technical meaning
The X.4.3 pattern means directory server failure: the network system was unable to forward the message because a directory server was unavailable. The standard identifies inability to connect to an Internet DNS server as one example of this error. This detail is useful only as a persistent transient failure.
Delivery status
The leading digit 4 denotes a persistent transient failure: the current attempt failed, but the condition may clear. The code alone identifies neither the particular directory service nor the party responsible for its unavailability, and it is not a permanent rejection of the message.
- Class
- Temporary failure
- Retry
- Controlled retry
- Suppression
- Check the full context
Retry decision
Operationally, route the message through a bounded retry mechanism with backoff, jitter, idempotency, and a time or attempt limit. Stop after success, a permanent result, or exhaustion of the limit; refer repeated 4.4.3 results for diagnosis instead of retrying indefinitely.
Suppression decision
Operationally, do not add the address to a suppression list based on 4.4.3 alone. Inspect the full response, bounded-retry history, and other delivery events; suppress only when an independent permanent signal or the applicable policy justifies it.
Common causes
- A directory server required to forward the message was unavailable during the current attempt.
- The network system could not connect to an Internet DNS server; the standard gives this as one example of directory server unavailability.
Diagnostic steps
- Inspect the raw SMTP response or delivery report and confirm that the enhanced code is exactly 4.4.3 and that the basic reply is in the 4xx class.
- Correlate the response with the intended message, attempt time, and system that returned it; use available logs to determine whether forwarding stopped while accessing a directory service.
- Check the availability and connectivity of the actual directory service used in this flow; if it is Internet DNS, verify its reachability for the same time without assuming from the code alone that DNS was the cause.
- Compare the results of bounded retries and stop them after success, a permanent rejection, or the configured limit is reached.
Actions by owner
Sender administrator
- Retain the raw response and attempt data, then route the message to a bounded retry queue with backoff and idempotency.
- Group repeated 4.4.3 results by destination system and time; after the limit is exhausted, give the code and attempt data to the recipient administrator or provider, and do not suppress based on this code alone.
Recipient administrator
- If the error originated in a system you manage, inspect the availability of the directory service required to forward the message and its connectivity at the failed-attempt time.
- Restore the confirmed unavailable service or connectivity path and verify the result of a new, controlled attempt.
Provider
- If you operate a mail, directory, or network system involved in the attempt, inspect service and connectivity logs for the specified time; do not attribute the problem to DNS from the code alone.
- Restore the confirmed service or path, and preserve the exact status code in the response so the sender can control retries correctly.
Sources and verification
The canonical T0 meaning of X.4.3 and its class assignment were verified against the IANA registry and RFC 2034, RFC 3463, and RFC 5248 as of July 17, 2026. Retry, diagnostic, and suppression guidance is presented separately as operational advice.
- iana-smtp-enhanced-status-codesT0 source
Enumerated Status Codes / X.4.3
- rfc5248T0 source
Section 2.1: registry fields and non-exclusive Associated Basic Status Code
- rfc2034T0 source
Section 4: enhanced status class agrees with SMTP reply class
- rfc3463T0 source
IANA registry reference for X.4.3
Last verified:
