Re: Bug/Issue: References header doesn't wrap in emacs package
authorSanjoy Mahajan <sanjoy@olin.edu>
Tue, 7 Jun 2016 15:51:25 +0000 (11:51 +2000)
committerW. Trevor King <wking@tremily.us>
Sat, 20 Aug 2016 23:22:01 +0000 (16:22 -0700)
6d/ddf5f1578ed77980157a1744e9cdd6bfe508c3 [new file with mode: 0644]

diff --git a/6d/ddf5f1578ed77980157a1744e9cdd6bfe508c3 b/6d/ddf5f1578ed77980157a1744e9cdd6bfe508c3
new file mode 100644 (file)
index 0000000..95935f5
--- /dev/null
@@ -0,0 +1,78 @@
+Return-Path: <Sanjoy.Mahajan@olin.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 arlo.cworth.org (Postfix) with ESMTP id 0B2006DE00D3\r
+ for <notmuch@notmuchmail.org>; Tue,  7 Jun 2016 08:52:19 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.011\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5\r
+ tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001,\r
+ T_RP_MATCHES_RCVD=-0.01] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id UTAOxujvxNl9 for <notmuch@notmuchmail.org>;\r
+ Tue,  7 Jun 2016 08:52:11 -0700 (PDT)\r
+Received: from EXCAS04.olin.edu (excas04.olin.edu [208.91.55.40])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id E17BE6DE00BF\r
+ for <notmuch@notmuchmail.org>; Tue,  7 Jun 2016 08:52:10 -0700 (PDT)\r
+Received: from insight.mit.edu (10.7.8.58) by EX03.olin.edu (10.1.15.11) with\r
+ Microsoft SMTP Server (TLS) id 15.0.1104.5;\r
+ Tue, 7 Jun 2016 11:52:08 -0400\r
+Received: from sanjoy by insight.mit.edu with local (Exim 4.87)\r
+ (envelope-from <sanjoy@olin.edu>)\r
+ id 1bAJHp-0007zO-Sv; Tue, 07 Jun 2016 11:51:25 -0400\r
+From: Sanjoy Mahajan <sanjoy@olin.edu>\r
+To: David Bremner <david@tethera.net>, Allan Streib <astreib@indiana.edu>,\r
+ <notmuch@notmuchmail.org>\r
+Subject: Re: Bug/Issue: References header doesn't wrap in emacs package\r
+In-Reply-To: <87vb1l9tt3.fsf@zancas.localnet>\r
+References: <87612qwh04.fsf@viking.dsc.soic.indiana.edu>\r
+ <87si5t1nhu.fsf@zancas.localnet> <878u7k21d8.fsf@zancas.localnet>\r
+ <87d1ntg1a2.fsf@insight.mit.edu> <87vb1l9tt3.fsf@zancas.localnet>\r
+User-Agent: Notmuch/0.22 (http://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Tue, 7 Jun 2016 11:51:25 -0400\r
+Message-ID: <87twh5dmki.fsf@insight.mit.edu>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-Originating-IP: [10.7.8.58]\r
+X-ClientProxiedBy: EXCAS04.olin.edu (10.1.15.17) To EX03.olin.edu (10.1.15.11)\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://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: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 07 Jun 2016 15:52:19 -0000\r
+\r
+On 2016-06-07 06:28, David Bremner <david@tethera.net> wrote:\r
+\r
+> Sanjoy Mahajan <sanjoy@olin.edu> writes:\r
+>\r
+>\r
+>> I'm not sure whether fixing it in emacs is right.  The command 'notmuch\r
+>> reply' is itself (with the sexp or json formats) generating the too-long\r
+>> References: header.  Shouldn't it generate an RFC-compliant message?\r
+>>\r
+>> Or should the json/sexp formats remain agnostic about line length,\r
+>> because wrapping doesn't make sense with key/value pairs?  In that case,\r
+>> I agree that message-mode should fix any long lines.\r
+>\r
+> For me the main issue is that the references header is editable by the\r
+> user before sending. So some input sanitization is needed at the sending\r
+> stage.\r
+\r
+Further supporting that argument, the user could also include a\r
+1000-character line in the message body, which would require sanitizing\r
+at the sending stage.\r
+\r
+-Sanjoy\r