Hi, I'm trying to get just a little better result in crafting a reply draft message. I'm using Ken's very nice 'replyfilter' script and recipe, which formats nearly all of the body of the message perfectly.
But, I still get a little cruft in the body, thus On 15 August 2012 at 15:36, "=?utf-8?B?a2F0aHlyb3NlOTcyMjlAY29tY2FzdC5uZXQ=?=" <ka...@computer.net> wrote: And, the email headers in the draft aren't quite right To: "=?utf-8?B?a2F0aHlyb3NlOTcyMjlAY29tY2FzdC5uZXQ=?=" <ka...@computer.net> Subject: Re: =?utf-8?B?UmU6IENhcmUgY29mZXJlbmNl?= These came from a message with Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 Content-Disposition: inline In a message on this list from last May, as I understand it, if a message contains non-ASCII, then it needs to run through mhbuild prior to running through replyfilter. It sounded to me that if the message had correct MIME headers, that replyfilter maybe could deal with that correctly without needing help from mhbuild. Would I be correct in assuming that a recipe of mhbuild with reply filter would allow the email headers and the last bit of the email body to correctly be converted into text/plain with a charset I can read? If so, then could someone please give me a little coaching regarding applying mhbuild for this purpose? Thanks.... -- Kevin _______________________________________________ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers