On Tue, Nov 22, 2016 at 03:38:57PM +0100, Vincent Lefevre wrote: > On 2016-11-22 20:43:12 +1100, Cameron Simpson wrote: > > On 22Nov2016 03:27, vincent lefevre <vinc...@vinc17.org> wrote: > > > 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). > > > > Yeah. And reading the text of RFC2047 suggests that it is intended for > > Subject: lines etc and explicitly _not_ for structured fields used by mail > > transport agents, to avoid any need to rewrite the entire mail > > infrastructure. > > It can be used in structured fields like "From:" or "To:", but only > in place of a comment, so that it doesn't interfere with the addresses.
So while it could even be used in the "phrase" part of obs-references, but 5322 explicitly says those parts should be ignored for the purposes of interpretation. After taking the time myself to also review 5322 and 2047, I think mutt is already doing the right thing in this case. It should not attempt to somehow encode the utf-8 character in the left-side of the references msg-id when sending. On the other side, a received illegally rfc2047-encoded references msg-id should not be decoded before attempting to interpret it. Given that, I'm going to close #3898 wont-fix. Thank you everyone for your helpful feedback! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
