On Sat, Feb 06, 2021 at 11:47:56AM +0000, Stuart Henderson wrote: > On 2021/02/06 07:24, Anindya Mukherjee wrote: > > >From: Theo Buehler <[email protected]> > > > > > >Thanks for the diff, I committed it. I had to re-do it since your mailer > > >used some MIME encoding, the result is visible here: > > >https://marc.info/?l=openbsd-bugs&m=161258168001057&q=mbox > > quoted-printable. > > > Sorry about that! It looks horrible! Thanks for letting me know. Is this > > message also garbled? I'm using the outlook.com website set to plain > > text, but it still managed to mess it up somehow. > > It's "plain" text (as in "not html") but it's encoded. At least it's > mostly readable and not as bad as one of the popular privacy-focussed > email servers that base64-encodes text...
It seems it was being encoded as ISO-8859-1. > > It's best if it can be avoided sender-side (some people will just ignore > mails sent like this) but can be handled receiver side if necessary. > In mutt if you pipe it from the view-attachment menu (usually on 'v') > it will be decoded automatically (whereas if you pipe from the mailbox > listing it will be sent raw). Or there's "qprint" in ports. It's easier > than bad word wrapping which can often not be fixed automatically. > I have set up mutt :) Hopefully this renders correctly now. Anindya
