Re: encoding of message-ids

diff --git a/da/6cff17fac79620aa605d621e0da5fb92eecd6c b/da/6cff17fac79620aa605d621e0da5fb92eecd6c
new file mode 100644 (file)
index 0000000..47872d4
--- /dev/null
+++ b/da/6cff17fac79620aa605d621e0da5fb92eecd6c
@@ -0,0 +1,67 @@
+Return-Path: <david@tethera.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 6F9CF6DE1416\r
+ for <notmuch@notmuchmail.org>; Wed, 17 Feb 2016 05:34:37 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.307\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.307 tagged_above=-999 required=5 tests=[AWL=0.244,\r
+  RP_MATCHES_RCVD=-0.55, SPF_PASS=-0.001] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id Ibssecv-NVph for <notmuch@notmuchmail.org>;\r
+ Wed, 17 Feb 2016 05:34:35 -0800 (PST)\r
+Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id 6708C6DE13FB\r
+ for <notmuch@notmuchmail.org>; Wed, 17 Feb 2016 05:34:35 -0800 (PST)\r
+Received: from remotemail by fethera.tethera.net with local (Exim 4.84)\r
+ (envelope-from <david@tethera.net>)\r
+ id 1aW2En-0003fc-5X; Wed, 17 Feb 2016 08:33:49 -0500\r
+Received: (nullmailer pid 30244 invoked by uid 1000);\r
+ Wed, 17 Feb 2016 13:34:29 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, notmuch@notmuchmail.org\r
+Subject: Re: encoding of message-ids\r
+In-Reply-To: <87ziv0iimt.fsf@alice.fifthhorseman.net>\r
+References: <87si0svnim.fsf@zancas.localnet>\r
+ <87ziv0iimt.fsf@alice.fifthhorseman.net>\r
+User-Agent: Notmuch/0.21+26~g9404723 (http://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Wed, 17 Feb 2016 09:34:29 -0400\r
+Message-ID: <877fi3v4t6.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 17 Feb 2016 13:34:37 -0000\r
+\r
+Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:\r
+\r
+\r
+> That said, RFC 2047 suggest that its encodings are only relevant in\r
+> places where a "text" token would be used.  Message-ID (and References\r
+> and In-Reply-To) are intended to only contain dot-atom-text tokens.  So\r
+> probably it would be more correct to avoid applying to these specific\r
+> fields.\r
+>\r
+> i dunno that it's a big deal though, given the analysis above.\r
+\r
+I guess there are two seperate issues. One is the (mildly bogus)\r
+application of RFC2047 decoding to message-ids. The other other is the\r
+coercion into utf8 from whatever wacky 8bit encoding some creative\r
+person might use in a message-id.\r
+\r
+d\r