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.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
