Re: UTF-8 in mail headers (namely FROM) sent by bugzilla

diff --git a/97/b0ae350b3b80c56b2cb0b2637ac264fd2aa2c7 b/97/b0ae350b3b80c56b2cb0b2637ac264fd2aa2c7
new file mode 100644 (file)
index 0000000..ef388b6
--- /dev/null
+++ b/97/b0ae350b3b80c56b2cb0b2637ac264fd2aa2c7
@@ -0,0 +1,124 @@
+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 8A026431FC0\r
+       for <notmuch@notmuchmail.org>; Mon, 29 Jul 2013 12:46:40 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\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 wClswLbLxyPx for <notmuch@notmuchmail.org>;\r
+       Mon, 29 Jul 2013 12:46:35 -0700 (PDT)\r
+Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108])\r
+       by olra.theworths.org (Postfix) with ESMTP id BBE3E431FBF\r
+       for <notmuch@notmuchmail.org>; Mon, 29 Jul 2013 12:46:35 -0700 (PDT)\r
+Received: from [192.168.23.229] (dsl254-070-154.nyc1.dsl.speakeasy.net\r
+       [216.254.70.154])\r
+       by che.mayfirst.org (Postfix) with ESMTPSA id BE8C4F984;\r
+       Mon, 29 Jul 2013 15:46:27 -0400 (EDT)\r
+Message-ID: <51F6C692.5090104@fifthhorseman.net>\r
+Date: Mon, 29 Jul 2013 15:46:26 -0400\r
+From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+User-Agent: Mozilla/5.0 (X11; Linux x86_64;\r
+       rv:17.0) Gecko/20130630 Icedove/17.0.7\r
+MIME-Version: 1.0\r
+To: Jani Nikula <jani@nikula.org>\r
+Subject: Re: UTF-8 in mail headers (namely FROM) sent by bugzilla\r
+References: <08cb1dcd-c5db-4e33-8b09-7730cb3d59a2@gmail.com>\r
+       <871u6psjwr.fsf@ericabrahamsen.net>\r
+       <5712cc41-d0ce-4ed3-af1c-37cf639dd9c0@gmail.com>\r
+       <87y58xv71x.fsf@zancas.localnet> <87d2q5wrre.fsf@nikula.org>\r
+In-Reply-To: <87d2q5wrre.fsf@nikula.org>\r
+X-Enigmail-Version: 1.5.1\r
+Content-Type: multipart/signed; micalg=pgp-sha512;\r
+       protocol="application/pgp-signature";\r
+       boundary="----enig2URNAUIUXDSAWWJJWRTKN"\r
+Cc: 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: Mon, 29 Jul 2013 19:46:40 -0000\r
+\r
+This is an OpenPGP/MIME signed message (RFC 4880 and 3156)\r
+------enig2URNAUIUXDSAWWJJWRTKN\r
+Content-Type: text/plain; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On 07/26/2013 06:16 AM, Jani Nikula wrote:\r
+> I'm experiencing a similar problem with the Subject: headers in bugzill=\r
+a\r
+> mail. Per RFC 2047,\r
+>=20\r
+>     Ordinary ASCII text and 'encoded-word's may appear together in the\r
+>     same header field.  However, an 'encoded-word' that appears in a\r
+>     header field defined as '*text' MUST be separated from any adjacent=\r
+\r
+>     'encoded-word' or 'text' by 'linear-white-space'.\r
+>=20\r
+> In the problematic mails, the encoded-word begins immediately after\r
+> preceding text, i.e. without linear-white-space. Manually adding that\r
+> space in the message file makes the subject display as expected.\r
+>=20\r
+> The decoding is done in the cli using g_mime_message_get_subject(). I'm=\r
+\r
+> not sure if there's much that can be done about it within notmuch.\r
+\r
+I think asking gmime to deliberately mis-parse the subject line would\r
+probably be a bad idea, because that would cause some strings to be\r
+impossible to represent in the subject.\r
+\r
+So Jani's report here sounds like a bug in bugzilla itself.  Jani, have\r
+you reported this problem to that project?  I don't see it on their\r
+bugtracker [0], though maybe my scan of the list wasn't as thorough as\r
+it should be.\r
+\r
+Regards,\r
+\r
+       --dkg\r
+\r
+[0]\r
+https://bugzilla.mozilla.org/buglist.cgi?product=3DBugzilla&component=3DE=\r
+mail%20Notifications&resolution=3D---\r
+\r
+\r
+------enig2URNAUIUXDSAWWJJWRTKN\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
+iQJ8BAEBCgBmBQJR9saSXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w\r
+ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQjk2OTEyODdBN0FEREUzNzU3RDkxMUVB\r
+NTI0MDFCMTFCRkRGQTVDAAoJEKUkAbEb/fpcdf4P/0TVY7jjhka4R3QB2sjK0Ioi\r
+fI+i86E0vsREEzcSICj27SU9tvsPVtiakpMhhByN/d3YNU6w6kd7VMN1ntPJ+dos\r
+n7Xg/VSsUbUBRmDjPbprCkJ8/8YUbhrksirTB6rM3bMMltEjFOBexfZWYr8oQJG4\r
+Ffc6dRbaIwt0ypnXpQzd8xGzr+lo5tPBZhg9hFvGAkIu1vPp3UY+E2jsz/00Tk7N\r
+oMfOLJAZ+fvbx/LI8kyJR3P5UfBGRvOr4hHXrBDALDPopyyCe7+4bLpXZBxLYJqP\r
+Ju8hHP+OivgFeoRb+lvZRTS6i6x8kUt1weZAJfuY5lFjiorwOODZccPXB9ZnnHFp\r
+61jl74FVsnjkD/JZKr6EX5hQIez0puBl/a1m3QJAEWImJtqKGSV7kWkym+qHqnrL\r
+tDqjcdjzkxBHYlz9NBEt1zupEt3yOEZIboAsoY49O6+QaFzYed9W6U0rgdhKQ9ct\r
+SEQcustBpTOSfXKTdahgu98zRVtT85ugL+pjM46rvRm0FVP9cwshoHOYC0dEuB4b\r
+X6J7e57X/twOw7U3gbh7M0JdWi9X5OiXfTiXx6b1WQibbC1vIVijxeTomrFbXvvd\r
+O8/JbXnjynr+vGuXGMpKBwdrYzt0B4wtCQ5DzIbFMXCdKRCRKCfHyef7fFH63vAs\r
+bYBbyfshGJX2fep6GbnV\r
+=4HTT\r
+-----END PGP SIGNATURE-----\r
+\r
+------enig2URNAUIUXDSAWWJJWRTKN--\r