Leo Bicknell writes:
Here's an interesting path forward
To summarize your transition plan:
(1) Teach every message reader how to parse message/utf8, just like
message/rfc822 but allowing UTF-8.
(2) Allow message writers to generate UTF-8 using message/utf8.
Here's a better transition plan:
(1) Teach every message reader to accept UTF-8 in message/rfc822.
Some readers do this already.
(2) Allow message writers to generate UTF-8 in message/rfc822.
---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago