Yes, I think you found the problem! Work fine now with just one call to the ```convert8BitHeader()```. One of my earlier attempt to fix the problem was to change this https://searchfox.org/comm-central/rev/45c9a2810df38a7d8b4a9a396e244a9b438f3729/mailnews/mime/src/mimeParser.jsm#235 so that the call to ```convert8BitHeader()``` is skipped when the flag indicates an address. But that's what using the calls to parseDecodedHeader() instead of parseEncodedHeader() does so it looks like a better fix. Also, with this change not seeing the chopped off upper byte for chars like U+01FF. Didn't test with all the possible field types but OK with TO (including multiple TOs) and BCC.
Bug 1658361 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Yes, I think you found the problem! Work fine now with just one call to the ```convert8BitHeader()```. One of my earlier attempt to fix the problem was to change this https://searchfox.org/comm-central/rev/45c9a2810df38a7d8b4a9a396e244a9b438f3729/mailnews/mime/src/mimeParser.jsm#235 so that the call to ```convert8BitHeader()``` is skipped when the flag indicates an address. But that's what using the calls to parseDecodedHeader() instead of parseEncodedHeader() does so it looks like the *correct* fix. (And my fix failed under some conditions.) Also, with this change not seeing the chopped off upper byte for chars like U+01FF. Didn't test with all the possible field types but OK with TO (including multiple TOs) and BCC.