But of course, the answer is easy: Content-type:
application/andrew-inset. It probably would be useful to have
application/andrew-text broken out as well (or perhaps text/andrew; I
find text marked-up with Andrew markup easier to read raw than text
marked up with richtext markup).
Sure. But this is a solution that fragments the email universe. Either
you have to know what facilities your correspondent has, or you need to
use multipart/alternative most of the time, or people without
Andrew-specific readers are out of luck. If I don't have an
Andrew-specific reader, I'd like to be able to get as much information
out of the message as possible, no matter how suboptimal the
presentation might be.
The problem here is identical to the MacMIME one: one wants to pass the
application-specific information needed to display things optimally if
the message enters an optimal environment but to be able to assess the
information anyway if the optimal environment is not available.
john