Ah, I didn't look hard enough! In 3463, there's
X.6.3 Conversion required but not supported
The message content must be converted in order to be forwarded
but such conversion is not possible or is not practical by a
host in the forwarding path. This condition may result when an
ESMTP gateway supports 8bit transport but is not able to
downgrade the message to 7 bit as required for the next hop.
which seems about right.
For not being able to deliver an SMTPUTF8 message to a particular mailbox?
If so, I don't that code is especialy appropriate. The entire design of
the current EAI specification is based on there not being any conversions
other than in the limited case of displaying a delivered message to a
client that doesn't support the extension.
Given that's the design, how does it make sense to claim that a required
conversion is missing when no such conversion is defined or even possible?
And even if that weren't the case, I think things are likely to work better if
you use a code that's specific to SMTPUTF8 rather than a generic one. To the
extent anyone looks at these things, they're not likely to interpret 5.6.3 as a
SMTPUTF8 failure.
Ned
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp