#3039: wrong/ignored character set for traditional PGP -------------------------------------+-------------------------------------- Reporter: [email protected] | Owner: mutt-dev Type: defect | Status: closed Priority: minor | Milestone: 1.6 Component: crypto | Version: 1.5.17 Resolution: fixed | Keywords: charset, PGP/inline -------------------------------------+-------------------------------------- Changes (by Rocco Rutte <[email protected]>):
* status: new => closed * resolution: => fixed Comment: (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. -- Ticket URL: <http://dev.mutt.org/trac/ticket/3039#comment:12> Mutt <http://www.mutt.org/> The Mutt mail user agent
