c2/883f096f73eb6f64681c73ada41557563817bf

   1 Return-Path: <dkg@fifthhorseman.net>\r
   2 X-Original-To: notmuch@notmuchmail.org\r
   3 Delivered-To: notmuch@notmuchmail.org\r
   4 Received: from localhost (localhost [127.0.0.1])\r
   5         by olra.theworths.org (Postfix) with ESMTP id 45A2B431FAF\r
   6         for <notmuch@notmuchmail.org>; Tue, 10 Sep 2013 15:51:09 -0700 (PDT)\r
   7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
   8 X-Spam-Flag: NO\r
   9 X-Spam-Score: 1.716\r
  10 X-Spam-Level: *\r
  11 X-Spam-Status: No, score=1.716 tagged_above=-999 required=5\r
  12         tests=[BAD_ENC_HEADER=1.716] autolearn=disabled\r
  13 Received: from olra.theworths.org ([127.0.0.1])\r
  14         by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
  15         with ESMTP id iU1mk-Ojk1jL for <notmuch@notmuchmail.org>;\r
  16         Tue, 10 Sep 2013 15:51:03 -0700 (PDT)\r
  17 Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108])\r
  18         by olra.theworths.org (Postfix) with ESMTP id C819B431FAE\r
  19         for <notmuch@notmuchmail.org>; Tue, 10 Sep 2013 15:51:03 -0700 (PDT)\r
  20 Received: from [192.168.13.193] (lair.fifthhorseman.net [108.58.6.98])\r
  21         by che.mayfirst.org (Postfix) with ESMTPSA id B02F6F983;\r
  22         Tue, 10 Sep 2013 18:50:59 -0400 (EDT)\r
  23 Message-ID: <522FA24D.8080307@fifthhorseman.net>\r
  24 Date: Tue, 10 Sep 2013 18:50:53 -0400\r
  25 From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
  26 User-Agent: Mozilla/5.0 (X11; Linux x86_64;\r
  27         rv:17.0) Gecko/20130821 Icedove/17.0.8\r
  28 MIME-Version: 1.0\r
  29 To: Austin Clements <amdragon@MIT.EDU>\r
  30 Subject: Re: [PATCH] lib/cli: pass GMIME_ENABLE_RFC2047_WORKAROUNDS to\r
  31         g_mime_init() =?utf-8?q?a test?=\r
  32 References: <1378839078-6298-1-git-send-email-jani@nikula.org>\r
  33         <522F73A4.90802@fifthhorseman.net> <20130910223553.GI1426@mit.edu>\r
  34 In-Reply-To: <20130910223553.GI1426@mit.edu>\r
  35 X-Enigmail-Version: 1.5.1\r
  36 Content-Type: multipart/signed; micalg=pgp-sha512;\r
  37         protocol="application/pgp-signature";\r
  38         boundary="----enig2KLXWITXHWXJBIDUVJJLO"\r
  39 Cc: notmuch <notmuch@notmuchmail.org>\r
  40 X-BeenThere: notmuch@notmuchmail.org\r
  41 X-Mailman-Version: 2.1.13\r
  42 Precedence: list\r
  43 List-Id: "Use and development of the notmuch mail system."\r
  44         <notmuch.notmuchmail.org>\r
  45 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
  46         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
  47 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
  48 List-Post: <mailto:notmuch@notmuchmail.org>\r
  49 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
  50 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
  51         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
  52 X-List-Received-Date: Tue, 10 Sep 2013 22:51:09 -0000\r
  53 \r
  54 This is an OpenPGP/MIME signed message (RFC 4880 and 3156)\r
  55 ------enig2KLXWITXHWXJBIDUVJJLO\r
  56 Content-Type: text/plain; charset=UTF-8\r
  57 Content-Transfer-Encoding: quoted-printable\r
  58 \r
  59 On 09/10/2013 06:35 PM, Austin Clements wrote:\r
  60 \r
  61 > I haven't looked at exactly what workarounds this enables, but if it's\r
  62 > what I'm guessing (RFC 2047 escapes in the middle of RFC 2822 text\r
  63 > tokens), are there really subject lines that this will misinterpret\r
  64 > that weren't obviously crafted to break the workaround? =20\r
  65 \r
  66 not to get all meta, but i imagine subject lines that refer an example\r
  67 of this particular issue (e.g. when talking about RFC 2047) will break\r
  68 ;)  I'm trying one variant here.\r
  69 \r
  70 > The RFC 2047\r
  71 > escape sequence was deliberately designed to be obscure, since RFC\r
  72 > 2047 itself caused previously "standards-compliant" subject lines to\r
  73 > potentially be interpreted differently.\r
  74 \r
  75 right, and it was designed explicitly to put the boundary markers atword\r
  76 boundaries, and not in the middle of a word (i think that's what this is\r
  77 all about, right?).  so implementations which put the boundary markers\r
  78 in the middle of a word, or which include whitespace within the encoded\r
  79 text, aren't speaking RFC 2047.\r
  80 \r
  81 anyway, if there's a rough consensus to go forward with this, i'm not\r
  82 about to block it.  I understand that a large part of the business of\r
  83 being an MUA is working around other people's bugs instead of expecting\r
  84 them to fix them :/  I just don't like mis-rendering other text.\r
  85 \r
  86         --dkg\r
  87 \r
  88 \r
  89 ------enig2KLXWITXHWXJBIDUVJJLO\r
  90 Content-Type: application/pgp-signature; name="signature.asc"\r
  91 Content-Description: OpenPGP digital signature\r
  92 Content-Disposition: attachment; filename="signature.asc"\r
  93 \r
  94 -----BEGIN PGP SIGNATURE-----\r
  95 Version: GnuPG v1.4.14 (GNU/Linux)\r
  96 Comment: Using GnuPG with Icedove - http://www.enigmail.net/\r
  97 \r
  98 iQJ8BAEBCgBmBQJSL6JNXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w\r
  99 ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQjk2OTEyODdBN0FEREUzNzU3RDkxMUVB\r
 100 NTI0MDFCMTFCRkRGQTVDAAoJEKUkAbEb/fpcDlkP/RGwWm+rGz/1yR/JvvcfhDJA\r
 101 UhxbacLjpd2w5yRqc4iPmUc1O3w2tiXbhV+3d0PWI/NoCQu+bWNsEhfOUS1KUZiC\r
 102 q0iThisNMMeSS+BgiqjvB6aB6XPmn83SKeG3C/6eduarvzmuDrL/QIog0DJJ0854\r
 103 8HZNJLYmSYJM1h9E0bjX0DjBAmVJ2Pawc2zcY6BHiJtBx63+JZoJvrftYTcgClpj\r
 104 8e3n1UJu/9Lv+x77KPQ8p77MMOy79n1NFcneyHGqYTXO071tqyfJy7OQMDPkOyFt\r
 105 tF7mcI160Mnsujd5dj2CH1d93uTIJ6eZgwhVq4slbC1Bfdure5kFIioT0EqZYwFS\r
 106 si4ShzmvAtKDBi1ydwhDwtTTg52i/9b0UbprEm22YDpdnZTnZX7GfA42mg5w++bX\r
 107 hCG0WdSkr7JrFoNncSnjRETPp7IZxvz7eT40vocnKv1l7ZVcaHorNyZEseTEOEX8\r
 108 eV1QHfxtTsEaJSM2iOiUEEOG4cT6cADlm4qdP6K+c6LokfVTL5ZLKn1BpWfFzkdn\r
 109 nTeLajJx8XFNR4EYBav4Q4X9W4wNUZH15aCG3JiAfJssBlNIHAI9nYxyN3f9oRHL\r
 110 1gd2zPXoUkcY321/+3tMjSITEe+9OibZ9eWxFGrTUXUvZfJaPNsLirVPGN+Tmeti\r
 111 Q+HaUBGs3c/T3THhsoq3\r
 112 =1sjc\r
 113 -----END PGP SIGNATURE-----\r
 114 \r
 115 ------enig2KLXWITXHWXJBIDUVJJLO--\r