Re: header continuation issue in notmuch frontend/alot/pythons email module
authorAustin Clements <amdragon@MIT.EDU>
Sun, 23 Jun 2013 17:27:35 +0000 (13:27 +2000)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:55:42 +0000 (09:55 -0800)
0b/ee7fb6ea92a8468d66472431061d47b06ab822 [new file with mode: 0644]

diff --git a/0b/ee7fb6ea92a8468d66472431061d47b06ab822 b/0b/ee7fb6ea92a8468d66472431061d47b06ab822
new file mode 100644 (file)
index 0000000..5970147
--- /dev/null
@@ -0,0 +1,88 @@
+Return-Path: <amdragon@mit.edu>\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 1D136431FB6\r
+       for <notmuch@notmuchmail.org>; Sun, 23 Jun 2013 10:27:49 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_LOW=-0.7] 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 zz313zr1fOOI for <notmuch@notmuchmail.org>;\r
+       Sun, 23 Jun 2013 10:27:41 -0700 (PDT)\r
+Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu\r
+       [18.7.68.34])\r
+       by olra.theworths.org (Postfix) with ESMTP id 446ED431FAE\r
+       for <notmuch@notmuchmail.org>; Sun, 23 Jun 2013 10:27:41 -0700 (PDT)\r
+X-AuditID: 12074422-b7ef78e000000935-5b-51c7300c61c2\r
+Received: from mailhub-auth-3.mit.edu ( [18.9.21.43])\r
+       by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP\r
+       id 7C.CB.02357.C0037C15; Sun, 23 Jun 2013 13:27:40 -0400 (EDT)\r
+Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])\r
+       by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id r5NHRdhA017303; \r
+       Sun, 23 Jun 2013 13:27:40 -0400\r
+Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91])\r
+       (authenticated bits=0)\r
+       (User authenticated as amdragon@ATHENA.MIT.EDU)\r
+       by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r5NHRaLv004094\r
+       (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT);\r
+       Sun, 23 Jun 2013 13:27:38 -0400\r
+Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.80)\r
+       (envelope-from <amdragon@mit.edu>)\r
+       id 1Uqo4e-0004g1-GD; Sun, 23 Jun 2013 13:27:36 -0400\r
+From: Austin Clements <amdragon@MIT.EDU>\r
+To: Justus Winter <4winter@informatik.uni-hamburg.de>\r
+Subject: Re: header continuation issue in notmuch frontend/alot/pythons email\r
+       module\r
+In-Reply-To: <20130623165938.GA2214@mit.edu>\r
+References: <20130623131145.2526.439@thinkbox.jade-hamburg.de>\r
+       <20130623165938.GA2214@mit.edu>\r
+User-Agent: Notmuch/0.15.2+182~gd0bd88f (http://notmuchmail.org) Emacs/23.4.1\r
+       (i486-pc-linux-gnu)\r
+Date: Sun, 23 Jun 2013 13:27:35 -0400\r
+Message-ID: <87li60d9fc.fsf@awakening.csail.mit.edu>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-Brightmail-Tracker:\r
+ H4sIAAAAAAAAA+NgFnrLIsWRmVeSWpSXmKPExsUixCmqrctjcDzQ4MM0c4vZrT+YLK7fnMns\r
+       wOQx8fxpNo9nq24xBzBFcdmkpOZklqUW6dslcGU0zFvAVDCLpWJ12xWWBsblzF2MnBwSAiYS\r
+       1y/PhbLFJC7cW88GYgsJ7GOUOHjIsYuRC8jeyCjRsriLGcI5zSTRu/0VlLOEUWLpvGVg7WwC\r
+       GhLb9i9nBLFFBEwlNjx4wA5iMwsYSdzfMR2sRlggROLf1hawFZwCOhLvHq5hhlgXJzHp11qw\r
+       uKhAosSkBZ1gcRYBVYn+ww9YQGxeoFNPHN7LDmELSpyc+YQFYr6WxI1/L5kmMArOQpKahSS1\r
+       gJFpFaNsSm6Vbm5iZk5xarJucXJiXl5qka6pXm5miV5qSukmRlCosrso7WD8eVDpEKMAB6MS\r
+       D2+m6rFAIdbEsuLK3EOMkhxMSqK8Z6WOBwrxJeWnVGYkFmfEF5XmpBYfYpTgYFYS4d1wDaic\r
+       NyWxsiq1KB8mJc3BoiTOK3ZrZ6CQQHpiSWp2ampBahFMVoaDQ0mCd5Ie0FDBotT01Iq0zJwS\r
+       hDQTByfIcB6g4e9AaniLCxJzizPTIfKnGBWlxHkvgSQEQBIZpXlwvbBU8opRHOgVYd4PIFU8\r
+       wDQE1/0KaDAT0OA9qw+BDC5JREhJNTD2fg9tF9qm/vXX7MCVkiFHqwVvyO7YxXi78u+a5M3r\r
+       63PDA7ljyoWmrGq78O7HG+WfKjKfX1sfOntkq/iz9eUR7wsmm4Rt2GBUEse1em/7LH/Jjps1\r
+       q+cbWy6aNudz7uXNW1cnB28WPTqb9/zGxe9lQ9NW5l3b6zTbOfeuROqCKxvfln1Uivz3W4ml\r
+       OCPRUIu5qDgRAC78WTYAAwAA\r
+Cc: notmuch mailing list <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: Sun, 23 Jun 2013 17:27:49 -0000\r
+\r
+On Sun, 23 Jun 2013, Austin Clements <amdragon@MIT.EDU> wrote:\r
+> There also appears to be a bug in the notmuch CLI's reply command\r
+> where it omits addresses that were folded in the original message.  I\r
+> don't know if alot uses the CLI's reply command, so this may or may\r
+> not be related to your specific issue.  I haven't dug into this yet,\r
+> other than to confirm that it's the CLI's fault and not\r
+> notmuch-emacs's.\r
+\r
+I take back what I said about there being a bug in the reply command.\r
+It was a problem with my test case.\r