Good question. I would have preferred to use xtext, but this text from
RFC 3461 makes that not possible without too much risk of breakage:
Due to limitations in the Delivery Status Notification format, the
value of the original recipient address prior to encoding as "xtext"
MUST consist entirely of printable (graphic and white space)
characters from the US-ASCII [4] repertoire. If an addr-type is
defined for addresses which use characters outside of this
repertoire, the specification for that addr-type MUST define the
means of encoding those addresses in printable US-ASCII characters
when are then encoded as xtext.
The problem is that xtext is a transfer encoding which is removed when a
traditional message/delivery-status part is generated and there's a hard
requirement in today's deployed MTAs that the result of xtext removal be
7-bit ASCII.