Klaus Ethgen wrote: > So the bug still exists. Sorry, that I have to say that and have to > reopen the bug. >
Hi Klaus, I'm sorry that the patch does not fix your bug, please reopen it, absolutely! We have a bug upstream linked with that bug which was resolved with the following explanation: ---- (In [7d44a83efcc6]) Support the Charset: armor header for inline PGP. Closes #3039. The header is defined as optional by RfC4880. This is based on patch-1.5.9.tamo.pgp_charsetchack.1. We only support reading this header and, if present, recode the PGP output from the given charset to $charset if we find it valid; otherwise fall back to UTF-8. Certain clients make use of the header when sending mail, so mutt should respect it because some messages are otherwise unreadable. The sending side is not touched, we unconditionally send UTF-8. ---- So they just fixed the receiving side and not the sending side, is this still an issue to you? I think that there is another bug in the queue about the send_charset defaulted to utf-8 and upstream refused to change it (Based on the RFC I suppose); can you please have a look at 441950 and see if it's more appropriate to follow up there? I look forward to your reply Cheers Antonio -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
