#2997: Missparsed/decoded headers in index view on IMAP server
--+-
Reporter: Jeremie | Owner: brendan
Type: defect | Status: closed
Priority: major| Milestone: 1
#2997: Missparsed/decoded headers in index view on IMAP server
--+-
Reporter: Jeremie | Owner: brendan
Type: defect | Status: closed
Priority: major| Milestone: 1
#2997: Missparsed/decoded headers in index view on IMAP server
Changes (by gp):
* status: reopened => closed
* resolution: => invalid
Comment:
{{{
From: =?ISO-8859-1?Q?Br=E9ndan_Cully_<[EMAIL PROTECTED]>?=
From: =?iso-8859-1?Q?Br=E9ndan?= Cully <[EMAIL PROTECTED]>
}}}
Stupid me! My
#2997: Missparsed/decoded headers in index view on IMAP server
Changes (by gp):
* priority: minor => major
* status: closed => reopened
* resolution: invalid =>
Comment:
Well, from _my_ reading of RFC 2047 and RFC 822,
RFC 822, 4.1 SYNTAX:
{{{
originator = authentic
#2997: Missparsed/decoded headers in index view on IMAP server
Changes (by brendan):
* status: reopened => closed
* resolution: => invalid
Comment:
This is strictly a gmail IMAP bug, and the inconsistency is in the server.
Mutt does a limited header fetch for the index, then refetches t
#2997: Missparsed/decoded headers in index view on IMAP server
Comment (by pdmef):
Replying to [comment:3 Jeremie]:
> The problem is not strictly with Gmail's IMAP.
With what other IMAP server is this happening? Is header caching enabled?
When exactly does it happen again (i.e. same message
#2997: Missparsed/decoded headers in index view on IMAP server
Changes (by Jeremie):
* status: closed => reopened
* resolution: invalid =>
Comment:
The problem is not strictly with Gmail's IMAP. Here is why:
* the names (the content of the "From:" header) show incorrectly in the
index
#2997: Missparsed/decoded headers in index view on IMAP server
Changes (by brendan):
* status: new => closed
* resolution: => invalid
Comment:
Thanks for the report. It turns out this is a bug in gmail's IMAP server.
I received this message from a google developer regarding this problem
#2997: Missparsed/decoded headers in index view on IMAP server
Comment (by PaulFertser):
Here you can see example raw socket data when this problem occurs (sorry
for formatting, i'm not familiar with trac):
5< * 3 FETCH (UID 3 RFC822.SIZE 1667 INTERNALDATE "14-Oct-2007 18:15:46
+" FLAGS
#2997: Missparsed/decoded headers in index view on IMAP server
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
10 matches
Mail list logo
