5.4.3Directory server failure

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. Class 5 makes this a permanent result, so do not retry in the unchanged context.

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 and describes this detail as useful only for a persistent transient failure. The registry nevertheless also confirms a concrete class-5 variant; under the class-alignment rule, code 5.4.3 has a permanent result.

The leading digit 5 denotes a permanent failure for this message in the current context. This does not mean that directory-service unavailability can never clear, but the response does not justify repeating the same unchanged attempt. The code alone identifies neither the particular service nor the party responsible for its unavailability.

Class

Permanent failure

Retry

Do not retry unchanged

Suppression

Check the full context

Operational recommendation: stop automatic and manual retries of the same message in the unchanged context. Consider a new send only after a relevant condition has demonstrably changed, such as restoration of the required directory service or connectivity path, after checking suppression again and using idempotency; do not treat elapsed time alone as a sufficient change.

Operational recommendation: do not add the address to a suppression list based on 5.4.3 alone. Inspect the full response, the system returning the code, delivery history, and other permanent signals; suppress only when a separate recipient-specific signal or the applicable policy justifies it.

• A directory server required to forward the message was unavailable to the network system handling the attempt.
• The network system could not connect to an Internet DNS server; the standard gives this as one example of directory server failure.

1. Inspect the raw SMTP response or delivery report and confirm that the enhanced code is exactly 5.4.3 and that the basic reply is in the 5xx class.
2. 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.
3. Check the availability and connectivity of the actual directory service used in this flow; if it is Internet DNS, verify its reachability for the specified time without assuming from the code alone that DNS was the cause.
4. Stop unchanged retries and, before any new send, confirm that the relevant condition was repaired and check suppression state again.

Compare 4.4.3, which describes the same directory-server-failure detail in the temporary class; 4.4.1, where the remote host does not answer; 4.4.2, where a connection was established but the message transaction could not be completed; and 4.4.5, which concerns mail-system congestion.

• 4.4.1No answer from remote host
• 4.4.2Bad connection
• 4.4.3Directory server failure
• 4.4.5Mail system congestion

The canonical T0 meaning of X.4.3, its description as a persistent transient failure, and the accepted assignment of code 5.4.3 to class 5 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: 17 July 2026