[Users] encoded addresses causing problems in reply

[Jeremy Nicoll]

On Wed, 7 Sep 2022, at 22:02, Derek B. Noonburg wrote:

[snip]

> It looks like the original email uses base64 (=?iso-2022-jp?B?...?=),
> while the reply (generated by claws) uses quoted-printable
> (=?iso-2022-jp?Q?...?=).

I can understand claws using (whatever) form of encoding for
text that it has to encode that you provided in your reply, but
for copying values in incoming headers into outgoing headers 
why doesn't it just copy the literal byte sequence of the 
original encoded values?

It surely shouldn't matter if the reply email contains multiple
encoded strings using different forms of encoding, as each
fragment declares the encoding it uses.

-- 
Jeremy Nicoll - my opinions are my own.