[Users] encoded addresses causing problems in reply

[Derek B. Noonburg]

On Wed, 7 Sep 2022 14:02:56 -0700
"Derek B. Noonburg" <derekn at foolabs.com> wrote:
> If I manually set the encoding to UTF-8 (compose window -> options ->
> character encoding), that seems to help.  But I think it's just luck:
> that is, I suspect the ISO-2022-JP encoding happens to contain ">" and
> "," while the UTF-8 encoding doesn't.

Ok, I think I found a way to reproduce this.

I'm attaching a sample message.  If you drop it into a maildir/mh
folder, it should show up correctly in claws (i.e., no visible problems
in the headers).

Hit "reply-all".

Then change the to/cc addresses from derekn1/2/3 at foolabs.com to your
own address -- leaving all of the text outside the "<...>" unchanged.

Then set the encoding to ISO-2022-JP (options -> character encoding ->
Japanese -> ISO-2022-JP).

Now hit "send".

Best I can tell, the to/cc headers generated by claws contain ">" and
"(" characters in the printed-quotable sections.  And I think that's
illegal -- but please correct me if that's not the case.

- Derek
-------------- next part --------------
A non-text attachment was scrubbed...
Name: foo5.msg
Type: application/octet-stream
Size: 298 bytes
Desc: not available
URL: <http://lists.claws-mail.org/pipermail/users/attachments/20220907/bd9ec1ed/attachment.obj>