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. > Regarding non-ASCII, we decode to bytes. Valid message-ids only contain > ASCII anyway. If mutt ingests and decodes this rubbish, it can write out > clean _not_ encoded message-ids for those which are syntacticly clean, > making for a healthier ecosystem. This is ambiguous. Do you keep the encoding used by the sender or convert into UTF-8? And if you convert into UTF-8, do you use NFC, NFD, etc.? And for parts already in UTF-8, do you apply a normalization? -- 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)
