Hi,
$ mhlist
msg part type/subtype size description
19696 multipart/alternative 4785
1 text/html 2787
2 text/plain1680
$
The email has subtype plain first, then html. I know this from show(1)
so
msg part type/subtype size description
19696 multipart/alternative 4785
1 text/html 2787
2 text/plain1680
$
The email has subtype plain first, then html. I know this from show(1)
so it's then a bit odd
Ralph wrote:
Hi,
$ mhlist
msg part type/subtype size description
19696 multipart/alternative 4785
1 text/html 2787
2 text/plain1680
$
The email has subtype plain first, then html. I
Hi David,
mhlist(1) doesn't mention order AFAICS. Personally, I'd prefer the
email's order rather than add a layer of change for what seems
little gain.
I believe it's to convey the order of preference of RFC 1341, Sec.
7.2.3. Given that, I think the order make sense.
Thanks for the
Thanks for the reference. I can see that makes sense when displaying
the parts, baring the best type based on the user's... preferences,
but mhlist(1) says list information about MIME messages and I'm not so
sure it's intended by the RFC's authors then. Perhaps it's just a
side-effect of the