Missing support for RFC2047 in To/From/Cc/Bcc headers?

I am not an eM Client user, so I’m not looking for support.

I’m a web-developer, working on an SMTP client library, and I’m using various mail clients to evaluate the interpretation of MIME headers, encoding, etc.

I noticed that names with UTF-8 characters, defined in To/From/Cc/Bcc headers, in RFC2047 format, do not display correctly in your client.

For example, I’m sending a MIME message with the following headers:

Date: Thu, 15 Sep 2016 17:20:54 +0200

To: =?UTF-8?Q?Rasmus =C3=A5h Schultz?= <blip><br>From: blub@test.org<br>Subject: =?UTF-8?Q?Hey, Rasmus! I like =C3=86=C3=98=C3=85=C3=A6=C3=B8=C3=A5!?=<br>MIME-Version: 1.0<br></blip>

In eM Client, the Subject header is correctly interpreted and displays with international characters - but the recipient name displays the encoded name verbatim.

I’ve been opening my test-messages in other programs, and have validated them through a MIME message linter/validator as well, so I’m fairly confident my encoding is correct.

Also, the encoding used in the Subject and To headers in this example are identical.

Can you please confirm whether RFC2047 support is incomplete in your client?