Blazalek.com

2.6.8Required UTF-8 reply not permitted by the SMTP client

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.

Category
Message content and format
Class
Success
Retry
Do not retry unchanged
Suppression
Check the full context

TL;DR

Reports that a UTF-8 reply was needed but the SMTP client forbids it: success status, not rejection. Operationally relevant for mailbox-name display limits. Do not retry. Deliverability and list hygiene are unaffected.

What this code means

Displaying a mailbox name would require a UTF-8 string in the reply, but the SMTP client's restrictions block that form; pattern X.6.8 under class 2 records that presentation constraint in an otherwise successful SMTP exchange rather than a delivery failure. The code does not assert that the mailbox is invalid or unreachable. Whether UTF-8 display is required, and which client setting blocked it, must be read from the full response and client configuration, not from the enhanced code alone. The success class still applies even though the reply cannot show the name in UTF-8.

Technical meaning

The X.6.8 pattern means that displaying the mailbox name requires a reply that contains a UTF-8 string, but the SMTP client does not allow 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

  1. 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.
  2. 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.
  3. 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

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

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.