#3898: UTF-8 character in References header
-----------------------+----------------------
  Reporter:  kevin8t8  |      Owner:  mutt-dev
      Type:  defect    |     Status:  closed
  Priority:  minor     |  Milestone:
 Component:  MIME      |    Version:
Resolution:  wontfix   |   Keywords:
-----------------------+----------------------
Changes (by kevin8t8):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 After more discussion on mutt-dev (from people much more knowledgeable
 than I), and reviewing rfc5322 and 2047, there isn't anything Mutt should
 really be doing in this case.

 The utf-8 character should not be in the left-side of the references msg-
 id, but there is no proper way to encode it.  Rfc2047 is not supposed to
 be used on structured header fields, except in comment/phrase parts that
 have no influence on their interpretation.  So Fastmail did the wrong
 thing in this case.

 The rfc653x series is phasing in unencoded utf-8 support in the local and
 domain part of addresses, so I don't think there would be a benefit in
 removing or somehow touching the message-id in this case.

 Given that, as you mentioned on irc, this may have been generated by a
 user fat-fingering a git command-line argument, I don't see this as worth
 fretting too much over.  So I'm going to close this as wont-fix.

 Thank you for the bug report, though!

--
Ticket URL: <https://dev.mutt.org/trac/ticket/3898#comment:1>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Reply via email to