-1 I already tried to solve the above problem using a more general approach (output all content-type parameters, not just charset) [1]. There was a lengthy discussion on IRC about it and it was rejected. The consensus was that we need to make some more substantial changes to JSON and raw output formats to properly fix the issue (and the issue is more general than what this patch fixes, other content-type parameters are useful for renderers as well and should be included in the output). One particular issue with your patch is that it adds (incorrect) charset parameter to plain/text parts which are converted to UTF-8 in JSON output. I am planning to work on a proper fix for this issue, but decided to postpone it until Austin's rewrite of notmuch show is complete. Regards, Dmitry [1] id:"1321659905-24367-1-git-send-email-dmitry.kurochkin@gmail.com"