#2997: Missparsed/decoded headers in index view
----------------------+-----------------------------------------------------
  Reporter:  Jeremie  |       Owner:  mutt-dev                
      Type:  defect   |      Status:  closed                  
  Priority:  minor    |   Milestone:  1.6                     
 Component:  display  |     Version:  1.5.17                  
Resolution:  wontfix  |    Keywords:  display headers encoding
----------------------+-----------------------------------------------------
Changes (by me):

  * status:  new => closed
  * resolution:  => wontfix


Old description:

> Using Gmail's IMAP: messages where the sender has accented characters in
> his realname in From: shows up as a mess =?ISO-8859-1?Q?J=E9r=E9mie?= in
> the "index" view alone. When I look at the raw message, I see that the
> From is indeed quoted. When I reply to a message with this problem, mutt
> suggests "To: =?ISO-8859-1?Q?J=E9r=E9mie?= <[email protected]>,
> ?=@laptop" (where laptop is the name of the computer I am working on).
>
> HOWEVER, the From: is then displayed correctly when viewing the message,
> either by pressing [ENTER] in the index view on the message, or by
> pressing 'h' (to view everything).
>
> ALSO, if I moved the message form the IMAP mailbox to a local mailbox,
> when I browse this local mailbox the messages that are copied there (that
> had a problem when they were being viewed in the IMAP mailbox) no longer
> show any signs of this bug. When I copy a message back from the local
> mailbox to the IMAP mailbox, the message is again displayed incorrectly
> in "index" view.
>
> FINALLY, the messages appear to be displayed correctly in Gmail's web
> client, in Thunderbird and in Alpine (using the same IMAP parameters for
> the last two clients).

New description:

 Using Gmail's IMAP: messages where the sender has accented characters in
 his realname in From: shows up as a mess =?ISO-8859-1?Q?J=E9r=E9mie?= in
 the "index" view alone. When I look at the raw message, I see that the
 From is indeed quoted. When I reply to a message with this problem, mutt
 suggests "To: =?ISO-8859-1?Q?J=E9r=E9mie?= <[email protected]>, ?=@laptop"
 (where laptop is the name of the computer I am working on).

 HOWEVER, the From: is then displayed correctly when viewing the message,
 either by pressing [ENTER] in the index view on the message, or by
 pressing 'h' (to view everything).

 ALSO, if I moved the message form the IMAP mailbox to a local mailbox,
 when I browse this local mailbox the messages that are copied there (that
 had a problem when they were being viewed in the IMAP mailbox) no longer
 show any signs of this bug. When I copy a message back from the local
 mailbox to the IMAP mailbox, the message is again displayed incorrectly in
 "index" view.

 FINALLY, the messages appear to be displayed correctly in Gmail's web
 client, in Thunderbird and in Alpine (using the same IMAP parameters for
 the last two clients).

--

Comment:

 I do not think it is going to be possible to make mutt parse incorrectly
 encoded address fields without potentially breaking legitimate encodings.
 The display in the pager works because it is not attempting to parse the
 email addresses, rather it is just decoding the strings as they appear.
 But the address parsing itself occurs prior to any decoding, and with a
 properly encoded message this is no problem.  The issue is that if the
 rfc2047 decoding occurs prior to the email address parsing, mutt may
 misparse the message because of characters in the "real name" part of the
 message that were protected by the rfc2047 encoding will be encountered.

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2997#comment:124>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Reply via email to