Comment 88 for bug 849416

(In reply to :Gijs Kruitbosch from comment #68)
> Now... Andrew/Mike, is the JS MIME parser thing something that ever
> happened? I can't find it from a quick search in bugzilla and MXR, but maybe
> I missed it (Andrew, poking you because of bug 447842 which looked related).

JSMime has, in effect partially landed. It's already in place for most header parsing and emission (as of TB 32 or so). It's *not* in place for parsing the body and message display--libmime is *very* featureful, so there is a very good deal of work that needs to get done to get it even in a state where it could be enabled by preference.

> Irrespective of that, AIUI the easiest way to avoid the lack of clarity /
> visibility of the ics attachment is to ignore and/or
> replace-with-multipart/mixed any use of multipart/alternative if and only if
> there is a part that with mimetype text/calendar . Is that right, and if
> not, can you suggest an alternative (minimal) way to address this

If you have Lightning installed, you probably want to treat text/calendar properly in a multipart/alternative. Otherwise, you'd want to treat it as a basic attachment.

> If that sounds acceptable, where does that need to be addressed? Still
> mailnews/mime/src/mimemalt.cpp and friends, or elsewhere?

Quite frankly, the multipart/alternative handling of libmime is a giant black hole, and the attachment handling is near as bad.