Ken wrote:
> I ... believe you are correct. I say this is fine to commit.
I'm glad it turned out to be a simple fix.
A different issue is that, in this case, mhfixmsg didn't need to
add the text/plain version of the text/html part because the
message already contained one. Here's the original message
structure excluding most of the image parts:
msg part type/subtype size description
3 multipart/alternative 1786K
boundary="Apple-Mail-2-23735733"
1 multipart/related 1784K
type="text/html"
boundary="Apple-Mail-3-23735734"
1.1 text/html 11K
charset="iso-8859-1"
1.2 image/tiff 9350
name="pastedGraphic1.tiff"
disposition "inline" filename="pastedGraphic1.tiff"
2 text/plain 1168
charset="iso-8859-1"
The problem is that the two text parts aren't alternatives of a
multipart. I'd say that message structure is presumptuous: it
doesn't let the recipient display the images if they can't
display the html.
Anyway, I was initially thinking that mhfixmsg couldn't deal
with this, but it can. It should look at the type of the
multipart/related and use that as the type of the alterative.
I just committed a fix, nmh's introduction to the world of
multipart/related.
David
_______________________________________________
Nmh-workers mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/nmh-workers
