Re: [nmh-workers] mhshow: invalid BASE64 encoding in --

[Valdis Klētnieks]

On Mon, 18 Mar 2019 21:10:45 -0400, Ken Hornstein said:

> But the email you sent out was marked as having a character set of UTF-8
> with characters encoded as ISO-8859-1.  Dude, I know you could do better
> (also, I am puzzled as to how that happened; I think with nmh you'd have
> to work to make that happen).

Note that exmh is now over 47,000 lines of tk/tcl, of which 'git blame'
says I'm the guilty party for 1,297.  I may be the current maintainer, but
that doesn't mean I wrote all of it. :)

Well, the chapter symbol as it showed up in your mail was a 2-byte
UTF 'C2A7', and what ended up in the outbound mail was only a Q-P encoded
=A7, so the question is what ate the C2 and why.

Testing indicates that when I do the reply, the  file when it's in Mail/drafts/
it's got the 2-byte string in it, but by the time it ends up in the Fcc: folder
it's lost the first byte and the second byte is QP-encoded. 

It seems to work fine if it ends up with:

Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

but the failing message had this instead:

Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

which at least gives me a place to start digging in more detail. Current
theory is an off-by-one 

(Cleaning up the non-ascii support is on the to-do list, but now that
I have a specific failure case to chase, it's time to get some caffeine
and beat this bug into submission..)