What this code means
A reply needed to show the mailbox name would have to contain a UTF-8 string, but the SMTP client does not permit that form of reply. Code 2.6.8 reports this as a success status, not a rejection.
Technical meaning
The X.6.8 pattern means that showing the mailbox name requires a reply containing a UTF-8 string, but the SMTP client does not permit such a reply. In the concrete code 2.6.8, class 2 qualifies this condition as success.
Delivery status
The leading digit 2 denotes success. Code 2.6.8 does not describe a temporary error, a permanent error, or a rejection; it reports a limitation on the form of the reply within a success-class result.
- Class
- Success
- Retry
- Do not retry unchanged
- Suppression
- Check the full context
Retry decision
Do not retry the SMTP operation automatically based on code 2.6.8 alone because it is a success status. If displaying the mailbox name in UTF-8 is necessary, first establish the client restriction and the full response context, and only then consider a deliberate new attempt; without a change in conditions, it may produce the same result.
Suppression decision
Do not add the address or domain to a suppression list based on code 2.6.8 alone. The code does not state that the mailbox is invalid or unavailable; make a suppression decision only from other independent events and the full context.
Common causes
- The server needs to use a UTF-8 string to show the mailbox name in its reply, but the SMTP client's restrictions do not allow that reply to be returned.
Diagnostic steps
- Inspect the raw SMTP response or report and confirm that the enhanced code is exactly 2.6.8 and that the event belongs to the success class.
- Correlate the code with the relevant SMTP operation and retain the complete response text to confirm that it concerns a mailbox name requiring a UTF-8 string.
- Inspect the SMTP client configuration and recorded behavior together with available server logs to determine why the client did not permit a reply containing UTF-8.
Actions by owner
Sender
- Treat 2.6.8 as a success status and do not repeat the same operation solely because this code appeared.
- If you need the UTF-8 mailbox name, give the administrator the complete response and context; do not infer from this code alone that the recipient address is invalid.
Sender administrator
- Preserve the success class, raw response, operation stage, and client settings, then identify the restriction that prevented a UTF-8 reply.
- If the mailbox name must be shown, correct the client-side configuration or handling and verify the result with a controlled new attempt without triggering automatic suppression.
Provider
- Preserve code 2.6.8 and the complete response text as a success-class event; do not present it as a bounce or rejection.
- Expose the available mailbox-name context and UTF-8 reply restriction so that an administrator can diagnose the client behavior without guessing.
Sources and verification
The meaning and registry assignment of X.6.8 were verified against the IANA registry and RFC 6531, and the interpretation of the enhanced-status class against RFC 2034 and RFC 5248, as of July 17, 2026. No accepted, exact provider response example is available, so this content is not attributed to any provider practice. The retry, suppression, diagnostic, and owner-action guidance is operational advice based on that classification, not a standards claim or documented provider practice.
- iana-smtp-enhanced-status-codesT0 source
Enumerated Status Codes / X.6.8
- 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
- rfc6531T0 source
IANA registry reference for X.6.8
Last verified:
