2b/bb9fdfd2397eb6d166fa4de2d9bf1c13778728

   1 Return-Path: <amdragon@mit.edu>\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 D220F431FAF\r
   6         for <notmuch@notmuchmail.org>; Tue, 10 Sep 2013 15:36:08 -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: -0.7\r
  10 X-Spam-Level: \r
  11 X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
  12         tests=[RCVD_IN_DNSWL_LOW=-0.7] 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 8WvW5NP9HuBX for <notmuch@notmuchmail.org>;\r
  16         Tue, 10 Sep 2013 15:36:02 -0700 (PDT)\r
  17 Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu\r
  18         [18.7.68.35])\r
  19         by olra.theworths.org (Postfix) with ESMTP id D50BD431FAE\r
  20         for <notmuch@notmuchmail.org>; Tue, 10 Sep 2013 15:36:01 -0700 (PDT)\r
  21 X-AuditID: 12074423-b7f168e00000095a-d5-522f9ed0189a\r
  22 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39])\r
  23         by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP\r
  24         id 96.52.02394.0DE9F225; Tue, 10 Sep 2013 18:36:00 -0400 (EDT)\r
  25 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])\r
  26         by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id r8AMZxQ9002308; \r
  27         Tue, 10 Sep 2013 18:36:00 -0400\r
  28 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91])\r
  29         (authenticated bits=0)\r
  30         (User authenticated as amdragon@ATHENA.MIT.EDU)\r
  31         by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r8AMZub7001412\r
  32         (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT);\r
  33         Tue, 10 Sep 2013 18:35:58 -0400\r
  34 Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.80)\r
  35         (envelope-from <amdragon@mit.edu>)\r
  36         id 1VJWXK-0000QY-Cj; Tue, 10 Sep 2013 18:35:54 -0400\r
  37 Date: Tue, 10 Sep 2013 18:35:53 -0400\r
  38 From: Austin Clements <amdragon@MIT.EDU>\r
  39 To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
  40 Subject: Re: [PATCH] lib/cli: pass GMIME_ENABLE_RFC2047_WORKAROUNDS to\r
  41         g_mime_init()\r
  42 Message-ID: <20130910223553.GI1426@mit.edu>\r
  43 References: <1378839078-6298-1-git-send-email-jani@nikula.org>\r
  44         <522F73A4.90802@fifthhorseman.net>\r
  45 MIME-Version: 1.0\r
  46 Content-Type: text/plain; charset=us-ascii\r
  47 Content-Disposition: inline\r
  48 In-Reply-To: <522F73A4.90802@fifthhorseman.net>\r
  49 User-Agent: Mutt/1.5.21 (2010-09-15)\r
  50 X-Brightmail-Tracker:\r
  51  H4sIAAAAAAAAA+NgFmpmleLIzCtJLcpLzFFi42IRYrdT170wTz/IYNcfKYvW7s9MFtdvzmR2\r
  52         YPI4293O6vFs1S3mAKYoLpuU1JzMstQifbsEroy1E+6xF+zhrLiyu521gfEKexcjB4eEgIlE\r
  53         e59zFyMnkCkmceHeerYuRi4OIYF9jBJrF29lh3A2MkrM+t7NCuGcZpI4v+MCE4SzhFFi968v\r
  54         jCD9LAKqEgefPGAGsdkENCS27V8OFhcR0Jc4c/cCK4jNDFTTuPYiWI2wQJhE3/FfYHFeAW2J\r
  55         g8cvsoHYQgLJErOb5rBAxAUlTs58wgLRqyVx499LJpCzmQWkJZb/4wAJcwKN/zZxFzuILSqg\r
  56         IjHl5Da2CYxCs5B0z0LSPQuhewEj8ypG2ZTcKt3cxMyc4tRk3eLkxLy81CJdM73czBK91JTS\r
  57         TYzgsHZR3sH456DSIUYBDkYlHt4bcvpBQqyJZcWVuYcYJTmYlER5n84BCvEl5adUZiQWZ8QX\r
  58         leakFh9ilOBgVhLhneoElONNSaysSi3Kh0lJc7AoifOuB0kJpCeWpGanphakFsFkZTg4lCR4\r
  59         1YDxKyRYlJqeWpGWmVOCkGbi4AQZzgM0PA+khre4IDG3ODMdIn+KUVFKnPfLXJDRIImM0jy4\r
  60         XljaecUoDvSKMK8VSDsPMGXBdb8CGswENPi7L9jgkkSElFQDo1203/T5y87Nj3jOFHrfmqks\r
  61         buuRqQVvlspfvfZL4Mt+Kz1LDq1fq5cdZBFyKXidwmTCt6N75sfPl70/JC969EOmcGnjocu7\r
  62         llatmFN6Xa7yYNfG9T+0c3aXVPjUrp3+6720VGeDZ//mnbsf9fz/M23D0+81O2Z8cFhxRjOy\r
  63         TuXoI/tVRrXP7y9RYinOSDTUYi4qTgQAOp7FmxYDAAA=\r
  64 Cc: notmuch <notmuch@notmuchmail.org>\r
  65 X-BeenThere: notmuch@notmuchmail.org\r
  66 X-Mailman-Version: 2.1.13\r
  67 Precedence: list\r
  68 List-Id: "Use and development of the notmuch mail system."\r
  69         <notmuch.notmuchmail.org>\r
  70 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
  71         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
  72 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
  73 List-Post: <mailto:notmuch@notmuchmail.org>\r
  74 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
  75 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
  76         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
  77 X-List-Received-Date: Tue, 10 Sep 2013 22:36:09 -0000\r
  78 \r
  79 Quoth Daniel Kahn Gillmor on Sep 10 at  3:31 pm:\r
  80 > On 09/10/2013 02:51 PM, Jani Nikula wrote:\r
  81 > > As explained by Jeffrey Stedfast, the author of GMime, quoted in [1]:\r
  82 > > \r
  83 > >> Passing the GMIME_ENABLE_RFC2047_WORKAROUNDS flag to g_mime_init()\r
  84 > >> *should* solve the decoding problem mentioned in the thread. This\r
  85 > >> flag should be safe to pass into g_mime_init() without any bad side\r
  86 > >> effects and my unit tests do test that code-path.\r
  87 > \r
  88 > the result of doing this is that there will become legitimately-crafted\r
  89 > subject lines that are now unrepresentable.\r
  90 > \r
  91 > I'm always leery of trying to improve support for data that doesn't\r
  92 > follow the standards at the expense of data that *does* follow the\r
  93 > standards.\r
  94 > \r
  95 >       --dkg\r
  96 \r
  97 I haven't looked at exactly what workarounds this enables, but if it's\r
  98 what I'm guessing (RFC 2047 escapes in the middle of RFC 2822 text\r
  99 tokens), are there really subject lines that this will misinterpret\r
 100 that weren't obviously crafted to break the workaround?  The RFC 2047\r
 101 escape sequence was deliberately designed to be obscure, since RFC\r
 102 2047 itself caused previously "standards-compliant" subject lines to\r
 103 potentially be interpreted differently.\r