On 2016-11-20 18:51:25 +1100, Cameron Simpson wrote: > On 19Nov2016 19:58, Kevin J. McCarthy <ke...@8t8.us> wrote: > > On Sun, Nov 20, 2016 at 10:08:13AM +1100, Cameron Simpson wrote: > > > On 19Nov2016 13:13, Kevin J. McCarthy <ke...@8t8.us> wrote: > > > > Should mutt be rfc-2047 encoding/decoding the references > > > > header? > > > > > > No. RFC2047 tokens need to be whitespace delimited from the surrounding > > > text. No whitespace is permitted inside the "<" and ">" markers which > > > enclose a message-id: > > > > Thank you for your detailed analysis, Cameron. I will take a deeper > > look at this soon. Another piece of information is that they sent a > > reply through the Fastmail web interface, which sent this: > > > > References: =?utf-8?Q?=3C201611170549=2EQ3WT?= > > =?utf-8?Q?foMB=C3=83=C2=BEngguang=2Ewu=40i?= > > =?utf-8?Q?ntel=2Ecom=3E=20=3C1479410?= =?utf-8?Q?777-6702-1-git-sen?= > > =?utf-8?Q?d-email-manuel=2Esch?= =?utf-8?Q?oelling=40gmx=2Ede=3E?= > > > > <https://gist.github.com/andrey-utkin/c9cf4f2dc282cf257a2552b06ede49d5> > > > > If this is legal, then mutt needs to be decoding the References before > > trying to parse out the ids, because I believe it will just choke on > > this. > > Wow. I would have thought that was illegal.
That's clearly illegal. MIME has been designed so that the main features should still work with software that doesn't support MIME (said otherwise, software that only needs to work with addresses and Message-ID's does not need to support MIME). > Regarding the discussion below, the TL;DR is that I think that if it is > feasible mutt should decode these, but write _unencoded_ versions of these > headers and any headers derived from them. In particular, is it easy to make > mutt's header ingestion code go "stict parse, but if that fails decode with > RFC2047 and try a second time"? Probably on a specific header basis. I don't think that Mutt should even try to support these. This could lead to various problems. First, what to do with characters that are illegal (e.g. non-ASCII) in a Message-ID... -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
