On Sat, 12 Jun 2021 10:04:36 +0100, Ralph Corderoy said:
What sorry excuse for an MUA are you using over there? :-)
That would be exmh.
And why doesn't it complain at you when it spots the attempt to send these transgressions onto the wire?
That's a very good question - I *thought* I fixed that, but obviously there's still some unicode/utf-8 confusion. It displayed correctly in Ken's mail, while composing the reply, and in your mail, which is why I didn't notice it was still broken. But wait.. there's more.. The =AF=5C screw-up is in the outbound file. 17:38:01 0 [~] grep "can only say" Mail/outbox/41541 | hx 00000000 3E206361 6E206F6E 6C792073 6179203D 41463D35 435F28E3 8384295F 2F3D4146 *> can only say =AF=5C_(...)_/=AF* 00000020 2E0A But linemode 'show' displays it correctly as well. Why did *that* work here but you report
it doesn't display correctly here when decoded, e.g. the un-QP'd =AF isn't valid UTF=8.
nmh-dafuq.png
Description: nmh-dafuq.png
Previous by Date: | Re: Bug reported regarding Unicode handling in email address, Steffen Nurpmeso |
---|---|
Next by Date: | Re: Bug reported regarding Unicode handling in email address, Ken Hornstein |
Previous by Thread: | Re: Bug reported regarding Unicode handling in email address, Ralph Corderoy |
Next by Thread: | Re: Bug reported regarding Unicode handling in email address, Ken Hornstein |
Indexes: | [Date] [Thread] [Top] [All Lists] |