Re: [PATCH] lib/cli: pass GMIME_ENABLE_RFC2047_WORKAROUNDS to g_mime_init() a test

diff --git a/c2/883f096f73eb6f64681c73ada41557563817bf b/c2/883f096f73eb6f64681c73ada41557563817bf
new file mode 100644 (file)
index 0000000..dd0d5df
--- /dev/null
+++ b/c2/883f096f73eb6f64681c73ada41557563817bf
@@ -0,0 +1,115 @@
+Return-Path: <dkg@fifthhorseman.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 olra.theworths.org (Postfix) with ESMTP id 45A2B431FAF\r
+       for <notmuch@notmuchmail.org>; Tue, 10 Sep 2013 15:51:09 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 1.716\r
+X-Spam-Level: *\r
+X-Spam-Status: No, score=1.716 tagged_above=-999 required=5\r
+       tests=[BAD_ENC_HEADER=1.716] 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 iU1mk-Ojk1jL for <notmuch@notmuchmail.org>;\r
+       Tue, 10 Sep 2013 15:51:03 -0700 (PDT)\r
+Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108])\r
+       by olra.theworths.org (Postfix) with ESMTP id C819B431FAE\r
+       for <notmuch@notmuchmail.org>; Tue, 10 Sep 2013 15:51:03 -0700 (PDT)\r
+Received: from [192.168.13.193] (lair.fifthhorseman.net [108.58.6.98])\r
+       by che.mayfirst.org (Postfix) with ESMTPSA id B02F6F983;\r
+       Tue, 10 Sep 2013 18:50:59 -0400 (EDT)\r
+Message-ID: <522FA24D.8080307@fifthhorseman.net>\r
+Date: Tue, 10 Sep 2013 18:50:53 -0400\r
+From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+User-Agent: Mozilla/5.0 (X11; Linux x86_64;\r
+       rv:17.0) Gecko/20130821 Icedove/17.0.8\r
+MIME-Version: 1.0\r
+To: Austin Clements <amdragon@MIT.EDU>\r
+Subject: Re: [PATCH] lib/cli: pass GMIME_ENABLE_RFC2047_WORKAROUNDS to\r
+       g_mime_init() =?utf-8?q?a test?=\r
+References: <1378839078-6298-1-git-send-email-jani@nikula.org>\r
+       <522F73A4.90802@fifthhorseman.net> <20130910223553.GI1426@mit.edu>\r
+In-Reply-To: <20130910223553.GI1426@mit.edu>\r
+X-Enigmail-Version: 1.5.1\r
+Content-Type: multipart/signed; micalg=pgp-sha512;\r
+       protocol="application/pgp-signature";\r
+       boundary="----enig2KLXWITXHWXJBIDUVJJLO"\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: Tue, 10 Sep 2013 22:51:09 -0000\r
+\r
+This is an OpenPGP/MIME signed message (RFC 4880 and 3156)\r
+------enig2KLXWITXHWXJBIDUVJJLO\r
+Content-Type: text/plain; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\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? =20\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
+> The RFC 2047\r
+> escape sequence was deliberately designed to be obscure, since RFC\r
+> 2047 itself caused previously "standards-compliant" subject lines to\r
+> potentially be interpreted differently.\r
+\r
+right, and it was designed explicitly to put the boundary markers atword\r
+boundaries, and not in the middle of a word (i think that's what this is\r
+all about, right?).  so implementations which put the boundary markers\r
+in the middle of a word, or which include whitespace within the encoded\r
+text, aren't speaking RFC 2047.\r
+\r
+anyway, if there's a rough consensus to go forward with this, i'm not\r
+about to block it.  I understand that a large part of the business of\r
+being an MUA is working around other people's bugs instead of expecting\r
+them to fix them :/  I just don't like mis-rendering other text.\r
+\r
+       --dkg\r
+\r
+\r
+------enig2KLXWITXHWXJBIDUVJJLO\r
+Content-Type: application/pgp-signature; name="signature.asc"\r
+Content-Description: OpenPGP digital signature\r
+Content-Disposition: attachment; filename="signature.asc"\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.14 (GNU/Linux)\r
+Comment: Using GnuPG with Icedove - http://www.enigmail.net/\r
+\r
+iQJ8BAEBCgBmBQJSL6JNXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w\r
+ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQjk2OTEyODdBN0FEREUzNzU3RDkxMUVB\r
+NTI0MDFCMTFCRkRGQTVDAAoJEKUkAbEb/fpcDlkP/RGwWm+rGz/1yR/JvvcfhDJA\r
+UhxbacLjpd2w5yRqc4iPmUc1O3w2tiXbhV+3d0PWI/NoCQu+bWNsEhfOUS1KUZiC\r
+q0iThisNMMeSS+BgiqjvB6aB6XPmn83SKeG3C/6eduarvzmuDrL/QIog0DJJ0854\r
+8HZNJLYmSYJM1h9E0bjX0DjBAmVJ2Pawc2zcY6BHiJtBx63+JZoJvrftYTcgClpj\r
+8e3n1UJu/9Lv+x77KPQ8p77MMOy79n1NFcneyHGqYTXO071tqyfJy7OQMDPkOyFt\r
+tF7mcI160Mnsujd5dj2CH1d93uTIJ6eZgwhVq4slbC1Bfdure5kFIioT0EqZYwFS\r
+si4ShzmvAtKDBi1ydwhDwtTTg52i/9b0UbprEm22YDpdnZTnZX7GfA42mg5w++bX\r
+hCG0WdSkr7JrFoNncSnjRETPp7IZxvz7eT40vocnKv1l7ZVcaHorNyZEseTEOEX8\r
+eV1QHfxtTsEaJSM2iOiUEEOG4cT6cADlm4qdP6K+c6LokfVTL5ZLKn1BpWfFzkdn\r
+nTeLajJx8XFNR4EYBav4Q4X9W4wNUZH15aCG3JiAfJssBlNIHAI9nYxyN3f9oRHL\r
+1gd2zPXoUkcY321/+3tMjSITEe+9OibZ9eWxFGrTUXUvZfJaPNsLirVPGN+Tmeti\r
+Q+HaUBGs3c/T3THhsoq3\r
+=1sjc\r
+-----END PGP SIGNATURE-----\r
+\r
+------enig2KLXWITXHWXJBIDUVJJLO--\r