Please do not use the term "message/utf-8". If used,
it would apply only to a certain MIME mechanism
It's the message/utf-8 as outlined in the dsn-00 I-D.
It's the name of a structure almost identical with a
message/rfc822, "only" allowing UTF-8 in the header
(or more precisely as specified in the header draft.)
as a MIME machanism it will not fly in that form,
because it violates RFC 2045.
Nothing's wrong with the message/utf-8 MIME type as
outlined in the DSN I-D.
we don't know how to convert a message/utf-8 for an
MTA that does not do 8BITMIME.
So let them put an 8BITMIME to 7bit step behind their
UTF8SMTP to 8BITMIME step. Where 8BITMIME to 7bit is
impossible any "direct" UTF8SMTP to 7bit approach is
also impossible.
UTF8SMTP can completely ignore 7bit because it builds
on 8BITMIME.