From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, notmuch@notmuchmail.org
Subject: Re: encoding of message-ids
Date: Wed, 17 Feb 2016 09:34:29 -0400 [thread overview]
Message-ID: <877fi3v4t6.fsf@zancas.localnet> (raw)
In-Reply-To: <87ziv0iimt.fsf@alice.fifthhorseman.net>
Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
> That said, RFC 2047 suggest that its encodings are only relevant in
> places where a "text" token would be used. Message-ID (and References
> and In-Reply-To) are intended to only contain dot-atom-text tokens. So
> probably it would be more correct to avoid applying to these specific
> fields.
>
> i dunno that it's a big deal though, given the analysis above.
I guess there are two seperate issues. One is the (mildly bogus)
application of RFC2047 decoding to message-ids. The other other is the
coercion into utf8 from whatever wacky 8bit encoding some creative
person might use in a message-id.
d
next prev parent reply other threads:[~2016-02-17 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 12:38 encoding of message-ids David Bremner
2016-02-16 19:02 ` Daniel Kahn Gillmor
2016-02-17 13:34 ` David Bremner [this message]
2016-02-24 17:15 ` W. Trevor King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fi3v4t6.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=dkg@fifthhorseman.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).