5e/008d115a223d6ba9a3dffd33844696e6c712ab

   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 836C5431FAF\r
   6         for <notmuch@notmuchmail.org>; Tue, 10 Sep 2013 18:51:56 -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.016\r
  10 X-Spam-Level: *\r
  11 X-Spam-Status: No, score=1.016 tagged_above=-999 required=5\r
  12         tests=[BAD_ENC_HEADER=1.716, RCVD_IN_DNSWL_LOW=-0.7]\r
  13         autolearn=disabled\r
  14 Received: from olra.theworths.org ([127.0.0.1])\r
  15         by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
  16         with ESMTP id kBLVBqIazSHN for <notmuch@notmuchmail.org>;\r
  17         Tue, 10 Sep 2013 18:51:49 -0700 (PDT)\r
  18 Received: from dmz-mailsec-scanner-2.mit.edu (dmz-mailsec-scanner-2.mit.edu\r
  19         [18.9.25.13])\r
  20         by olra.theworths.org (Postfix) with ESMTP id 12279431FAE\r
  21         for <notmuch@notmuchmail.org>; Tue, 10 Sep 2013 18:51:48 -0700 (PDT)\r
  22 X-AuditID: 1209190d-b7f078e000000937-e1-522fccb316ef\r
  23 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35])\r
  24         by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP\r
  25         id 8C.AB.02359.3BCCF225; Tue, 10 Sep 2013 21:51:47 -0400 (EDT)\r
  26 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])\r
  27         by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id r8B1pk6s029412; \r
  28         Tue, 10 Sep 2013 21:51:47 -0400\r
  29 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91])\r
  30         (authenticated bits=0)\r
  31         (User authenticated as amdragon@ATHENA.MIT.EDU)\r
  32         by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r8B1phNv002816\r
  33         (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT);\r
  34         Tue, 10 Sep 2013 21:51:45 -0400\r
  35 Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.80)\r
  36         (envelope-from <amdragon@mit.edu>)\r
  37         id 1VJZao-0001Sz-Ck; Tue, 10 Sep 2013 21:51:42 -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() =?utf-8?q?a test?=\r
  42 In-Reply-To: <522FA24D.8080307@fifthhorseman.net>\r
  43 References: <1378839078-6298-1-git-send-email-jani@nikula.org>\r
  44         <522F73A4.90802@fifthhorseman.net> <20130910223553.GI1426@mit.edu>\r
  45         <522FA24D.8080307@fifthhorseman.net>\r
  46 User-Agent: Notmuch/0.16+37~g9701e9c (http://notmuchmail.org) Emacs/23.4.1\r
  47         (i486-pc-linux-gnu)\r
  48 Date: Tue, 10 Sep 2013 21:51:41 -0400\r
  49 Message-ID: <8761u8jfbm.fsf@awakening.csail.mit.edu>\r
  50 MIME-Version: 1.0\r
  51 Content-Type: text/plain; charset=us-ascii\r
  52 X-Brightmail-Tracker:\r
  53  H4sIAAAAAAAAA+NgFnrPIsWRmVeSWpSXmKPExsUixCmqrLv5jH6Qweufyhat3Z+ZLK7fnMns\r
  54         wORxtrud1ePZqlvMAUxRXDYpqTmZZalF+nYJXBnferYyFhzkrPj2rpOpgfEWexcjJ4eEgInE\r
  55         gWffWSBsMYkL99azdTFycQgJ7GOUWHOnlwnC2cgoceb6JHYI5zSTxKpLd1kgnCWMEhs+7QWb\r
  56         xSagIbFt/3JGEFtEQF/izN0LrCA2s4CqROPai8wgtrBAusTf6X/B9nEKGErsmrQfauoyRomZ\r
  57         Hw+CNYgKxElc61wIVsQC1Pxr4z+wobxAx76YtZ0VwhaUODnzCQvEAi2JG/9eMk1gFJyFJDUL\r
  58         SWoBI9MqRtmU3Crd3MTMnOLUZN3i5MS8vNQiXSO93MwSvdSU0k2M4HCV5N3B+O6g0iFGAQ5G\r
  59         JR7eG3L6QUKsiWXFlbmHGCU5mJREeZ1PAoX4kvJTKjMSizPii0pzUosPMUpwMCuJ8E51Asrx\r
  60         piRWVqUW5cOkpDlYlMR514GkBNITS1KzU1MLUotgsjIcHEoSvAdPA2UFi1LTUyvSMnNKENJM\r
  61         HJwgw3mAhsecARleXJCYW5yZDpE/xagoJc5rA5IQAElklObB9cLSyStGcaBXhHk9QKp4gKkI\r
  62         rvsV0GAmoMHffcEGlyQipKQaGAX12/KYdB22JvZY3Pa5m2tkxm0w9UrKOueYqKlhq59eSd2g\r
  63         NyFbYZe1QGU26/yuTBMjs2OTzyb26WdPurvptthvjcVsJxJ4S34djZ5w9uiiqXaK2w+aXpPI\r
  64         mfwywE1Bq+zx+pUnj196cmDT4/23ZyQKTV/cNjsqheH2eq8n39WKdZ6GzWTqOqTEUpyRaKjF\r
  65         XFScCABmfm7jAgMAAA==\r
  66 Cc: notmuch <notmuch@notmuchmail.org>\r
  67 X-BeenThere: notmuch@notmuchmail.org\r
  68 X-Mailman-Version: 2.1.13\r
  69 Precedence: list\r
  70 List-Id: "Use and development of the notmuch mail system."\r
  71         <notmuch.notmuchmail.org>\r
  72 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
  73         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
  74 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
  75 List-Post: <mailto:notmuch@notmuchmail.org>\r
  76 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
  77 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
  78         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
  79 X-List-Received-Date: Wed, 11 Sep 2013 01:51:56 -0000\r
  80 \r
  81 On Tue, 10 Sep 2013, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:\r
  82 > On 09/10/2013 06:35 PM, Austin Clements wrote:\r
  83 >\r
  84 >> I haven't looked at exactly what workarounds this enables, but if it's\r
  85 >> what I'm guessing (RFC 2047 escapes in the middle of RFC 2822 text\r
  86 >> tokens), are there really subject lines that this will misinterpret\r
  87 >> that weren't obviously crafted to break the workaround?  \r
  88 >\r
  89 > not to get all meta, but i imagine subject lines that refer an example\r
  90 > of this particular issue (e.g. when talking about RFC 2047) will break\r
  91 > ;)  I'm trying one variant here.\r
  92 \r
  93 That's cheating.  ]:--8) Though, I wonder, you mentioned in your\r
  94 original email that there would be subject lines that are\r
  95 *unrepresentable* given the worked-around RFC 2047.  Did you mean that?\r
  96 If so, can you provide an example?  Isn't it always possible to, say,\r
  97 RFC 2047 escape the whole subject, which would be decoded correctly\r
  98 whether the decoder strictly adheres to RFC 2047 or uses the\r
  99 workarounds?\r
 100 \r
 101 (Speaking of which, it looks like message-mode does *not* RFC 2047\r
 102 encode the subject if it contains text that could be mistaken for an\r
 103 encoded-word, so such subjects won't get round-tripped correctly.)\r