Re: [PATCH] lib/cli: pass GMIME_ENABLE_RFC2047_WORKAROUNDS to g_mime_init() a test
authorAustin Clements <amdragon@MIT.EDU>
Wed, 11 Sep 2013 01:51:41 +0000 (21:51 +2000)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:57:04 +0000 (09:57 -0800)
5e/008d115a223d6ba9a3dffd33844696e6c712ab [new file with mode: 0644]

diff --git a/5e/008d115a223d6ba9a3dffd33844696e6c712ab b/5e/008d115a223d6ba9a3dffd33844696e6c712ab
new file mode 100644 (file)
index 0000000..45b3328
--- /dev/null
@@ -0,0 +1,103 @@
+Return-Path: <amdragon@mit.edu>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 836C5431FAF\r
+       for <notmuch@notmuchmail.org>; Tue, 10 Sep 2013 18:51:56 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 1.016\r
+X-Spam-Level: *\r
+X-Spam-Status: No, score=1.016 tagged_above=-999 required=5\r
+       tests=[BAD_ENC_HEADER=1.716, RCVD_IN_DNSWL_LOW=-0.7]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id kBLVBqIazSHN for <notmuch@notmuchmail.org>;\r
+       Tue, 10 Sep 2013 18:51:49 -0700 (PDT)\r
+Received: from dmz-mailsec-scanner-2.mit.edu (dmz-mailsec-scanner-2.mit.edu\r
+       [18.9.25.13])\r
+       by olra.theworths.org (Postfix) with ESMTP id 12279431FAE\r
+       for <notmuch@notmuchmail.org>; Tue, 10 Sep 2013 18:51:48 -0700 (PDT)\r
+X-AuditID: 1209190d-b7f078e000000937-e1-522fccb316ef\r
+Received: from mailhub-auth-1.mit.edu ( [18.9.21.35])\r
+       by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP\r
+       id 8C.AB.02359.3BCCF225; Tue, 10 Sep 2013 21:51:47 -0400 (EDT)\r
+Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])\r
+       by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id r8B1pk6s029412; \r
+       Tue, 10 Sep 2013 21:51:47 -0400\r
+Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91])\r
+       (authenticated bits=0)\r
+       (User authenticated as amdragon@ATHENA.MIT.EDU)\r
+       by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r8B1phNv002816\r
+       (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT);\r
+       Tue, 10 Sep 2013 21:51:45 -0400\r
+Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.80)\r
+       (envelope-from <amdragon@mit.edu>)\r
+       id 1VJZao-0001Sz-Ck; Tue, 10 Sep 2013 21:51:42 -0400\r
+From: Austin Clements <amdragon@MIT.EDU>\r
+To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+Subject: Re: [PATCH] lib/cli: pass GMIME_ENABLE_RFC2047_WORKAROUNDS to\r
+       g_mime_init() =?utf-8?q?a test?=\r
+In-Reply-To: <522FA24D.8080307@fifthhorseman.net>\r
+References: <1378839078-6298-1-git-send-email-jani@nikula.org>\r
+       <522F73A4.90802@fifthhorseman.net> <20130910223553.GI1426@mit.edu>\r
+       <522FA24D.8080307@fifthhorseman.net>\r
+User-Agent: Notmuch/0.16+37~g9701e9c (http://notmuchmail.org) Emacs/23.4.1\r
+       (i486-pc-linux-gnu)\r
+Date: Tue, 10 Sep 2013 21:51:41 -0400\r
+Message-ID: <8761u8jfbm.fsf@awakening.csail.mit.edu>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-Brightmail-Tracker:\r
+ H4sIAAAAAAAAA+NgFnrPIsWRmVeSWpSXmKPExsUixCmqrLv5jH6Qweufyhat3Z+ZLK7fnMns\r
+       wORxtrud1ePZqlvMAUxRXDYpqTmZZalF+nYJXBnferYyFhzkrPj2rpOpgfEWexcjJ4eEgInE\r
+       gWffWSBsMYkL99azdTFycQgJ7GOUWHOnlwnC2cgoceb6JHYI5zSTxKpLd1kgnCWMEhs+7QWb\r
+       xSagIbFt/3JGEFtEQF/izN0LrCA2s4CqROPai8wgtrBAusTf6X/B9nEKGErsmrQfauoyRomZ\r
+       Hw+CNYgKxElc61wIVsQC1Pxr4z+wobxAx76YtZ0VwhaUODnzCQvEAi2JG/9eMk1gFJyFJDUL\r
+       SWoBI9MqRtmU3Crd3MTMnOLUZN3i5MS8vNQiXSO93MwSvdSU0k2M4HCV5N3B+O6g0iFGAQ5G\r
+       JR7eG3L6QUKsiWXFlbmHGCU5mJREeZ1PAoX4kvJTKjMSizPii0pzUosPMUpwMCuJ8E51Asrx\r
+       piRWVqUW5cOkpDlYlMR514GkBNITS1KzU1MLUotgsjIcHEoSvAdPA2UFi1LTUyvSMnNKENJM\r
+       HJwgw3mAhsecARleXJCYW5yZDpE/xagoJc5rA5IQAElklObB9cLSyStGcaBXhHk9QKp4gKkI\r
+       rvsV0GAmoMHffcEGlyQipKQaGAX12/KYdB22JvZY3Pa5m2tkxm0w9UrKOueYqKlhq59eSd2g\r
+       NyFbYZe1QGU26/yuTBMjs2OTzyb26WdPurvptthvjcVsJxJ4S34djZ5w9uiiqXaK2w+aXpPI\r
+       mfwywE1Bq+zx+pUnj196cmDT4/23ZyQKTV/cNjsqheH2eq8n39WKdZ6GzWTqOqTEUpyRaKjF\r
+       XFScCABmfm7jAgMAAA==\r
+Cc: notmuch <notmuch@notmuchmail.org>\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://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: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 11 Sep 2013 01:51:56 -0000\r
+\r
+On Tue, 10 Sep 2013, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:\r
+> On 09/10/2013 06:35 PM, Austin Clements wrote:\r
+>\r
+>> I haven't looked at exactly what workarounds this enables, but if it's\r
+>> what I'm guessing (RFC 2047 escapes in the middle of RFC 2822 text\r
+>> tokens), are there really subject lines that this will misinterpret\r
+>> that weren't obviously crafted to break the workaround?  \r
+>\r
+> not to get all meta, but i imagine subject lines that refer an example\r
+> of this particular issue (e.g. when talking about RFC 2047) will break\r
+> ;)  I'm trying one variant here.\r
+\r
+That's cheating.  ]:--8) Though, I wonder, you mentioned in your\r
+original email that there would be subject lines that are\r
+*unrepresentable* given the worked-around RFC 2047.  Did you mean that?\r
+If so, can you provide an example?  Isn't it always possible to, say,\r
+RFC 2047 escape the whole subject, which would be decoded correctly\r
+whether the decoder strictly adheres to RFC 2047 or uses the\r
+workarounds?\r
+\r
+(Speaking of which, it looks like message-mode does *not* RFC 2047\r
+encode the subject if it contains text that could be mistaken for an\r
+encoded-word, so such subjects won't get round-tripped correctly.)\r