--- /dev/null
+Return-Path: <eric@deptj.eu>\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 BC5C26DE0243\r
+ for <notmuch@notmuchmail.org>; Mon, 4 Apr 2016 08:48:49 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.091\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.091 tagged_above=-999 required=5 tests=[AWL=0.001, \r
+ DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001,\r
+ RCVD_IN_MSPIKE_H3=-0.01, \r
+ RCVD_IN_MSPIKE_WL=-0.01, T_DKIM_INVALID=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 KZ4hqUJsME51 for <notmuch@notmuchmail.org>;\r
+ Mon, 4 Apr 2016 08:48:41 -0700 (PDT)\r
+Received: from mx1.solardns.com (mx1.solardns.com [109.73.127.119])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id 0B4FD6DE01C2\r
+ for <notmuch@notmuchmail.org>; Mon, 4 Apr 2016 08:48:40 -0700 (PDT)\r
+Received: from [213.129.84.218] (helo=luna.solardns.com)\r
+ by mx1.solardns.com with esmtps (TLSv1.2:DHE-RSA-AES256-SHA:256)\r
+ (Exim 4.85) (envelope-from <eric@deptj.eu>) id 1an6jy-0001TP-5t\r
+ for notmuch@notmuchmail.org; Mon, 04 Apr 2016 16:48:37 +0100\r
+DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=deptj.eu;\r
+ s=default; h=Date:Message-ID:References:In-Reply-To:To:Subject:From;\r
+ bh=LpqtfOJMdLepbJXMyWJGtYJua5Flr77g71ejsyFzJ0Y=; b=VNYqY7nAguM1SYhTOoJgF9VR9N\r
+ +zHOcA7OMM+cZQoLA/fMVEIN8VP0WKnev79Gjj+0tL57LnJpfALRGF1GdRppOpn+KJmQC126pqqU0\r
+ cAdpLvhFFUBwOwBYlVEuGBHY2Q54g74h6M+2IiHZ1t3/gpcPbq6J9osDe2zZjs4yJdvA=;\r
+Received: from [86.214.249.225] (port=38288 helo=bruno.deptj.eu)\r
+ by luna.solardns.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)\r
+ (Exim 4.86_1) (envelope-from <eric@deptj.eu>) id 1an6c5-003zNx-DG\r
+ for notmuch@notmuchmail.org; Mon, 04 Apr 2016 16:40:25 +0100\r
+Received: from eric by bruno.deptj.eu with local (Exim 4.84)\r
+ (envelope-from <eric@deptj.eu>) id 1an6c4-0002YK-KU\r
+ for notmuch@notmuchmail.org; Mon, 04 Apr 2016 17:40:24 +0200\r
+From: Eric <eric@deptj.eu>\r
+Subject: Re: Breaking a really long thread\r
+To: notmuch@notmuchmail.org\r
+In-Reply-To: <87k2kd8r6d.fsf@qmul.ac.uk>\r
+References: <c10e501c2baee471cbeeb42aad89a1e966407234-NM@bruno.deptj.eu>\r
+ <87k2kd8r6d.fsf@qmul.ac.uk>\r
+Message-ID: <85c5b3ffdcb6f033169ecde57283515081233436-NM@bruno.deptj.eu>\r
+Date: Mon, 04 Apr 2016 17:38:21 +0200 (CEST)\r
+X-AuthUser: deptjeu\r
+X-Filter-ID:\r
+ s0sct1PQhAABKnZB5plbIZxxbsbMXbbOVqDrOlLQDPCKLoLP9dSDpksiPa3sfcfQiw3bi2TEXpBy\r
+ KOgMDJLxZ2gLr13hkJnqYlE8dI2PqoFC/lGsrXcsS0xY0J18f6o7xB66CWvXcfKDfXjTU++u68NK\r
+ eZ+sg/ydBcEFZoBTCD6/UXKtgO6TCHXruigtupTXZuM7jUXIESohoO51xWmU8U0XxLGz4gGrl7np\r
+ YUMMsx7Zx6js8RMGZ+eyCM03IideZE/8G6RrW+hPYRmHOym9VEp4OmAp9SwcFw57ijAOXur1H/aA\r
+ warQpYDOYx/6JtUOKIpz/KyJk6xidDbrtJGeIvwS+mRNB2u5eXMTyiRDCl4blv/7/GYDGL6pBAPx\r
+ 3RhxuHrpSpJU4PQlqFj9797wgsGhIeDBws4kvu4hgViYIJSOH7FelTFEA57OugCjQqJvq5XDlSi1\r
+ S/CAqp6x6giLUpAadaOpLL7vzAlHz9Vt0lJbH3q7FSJEAvmcpRDg+DcXMCx8qKfWo/2nfeswSb/v\r
+ XOidX4Ts4xdG+C13IyWeZaJClvAWyUAUCSYHhmge3quet8geXjZWRvaT/RbJ/nX/IFFm7SbdEzck\r
+ 901Ob2Iq9tC/Vh1lis0iI/S1HLwoHXf0\r
+X-Report-Abuse-To: spam@mx1.solardns.com\r
+X-Filter-Fingerprint:\r
+ IFrWXGses7OKB5S5G8/dJdIz5bb8V0ykx8BnFBnunHBA3cTUQ1R++keuE7RDJ8Kg3RbMLUalw1oC\r
+ mj99/u+PoqoVy8a3lsStJtAvpObFX0XnhRv/ZJ3kEy8bfiAr+Fb/UpndEJ0YoaLytXXo8BMTaVt0\r
+ ARHRi6XGuAluI1udprEFZG3LO9fkj7mb1+yRqli/d+zCSxvHphGqsF3hVtrEAf060QZ1FCJg7pbn\r
+ CIpFp9M/hyUYo7G4LptAg5oSVRfFcobWokYzpFpNjdVH7bJEoA==\r
+X-Originating-IP: 213.129.84.218\r
+X-SpamExperts-Domain: out.solardns.com\r
+X-SpamExperts-Username: 213.129.84.218\r
+Authentication-Results: solardns.com;\r
+ auth=pass smtp.auth=213.129.84.218@out.solardns.com\r
+X-SpamExperts-Outgoing-Class: ham\r
+X-SpamExperts-Outgoing-Evidence: Combined (0.07)\r
+X-Recommended-Action: accept\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: Mon, 04 Apr 2016 15:48:49 -0000\r
+\r
+On Mon, 04 Apr 2016 14:00:26 +0100, Mark Walters <markwalters1009@gmail.com> wrote:\r
+> On Mon, 04 Apr 2016, Eric <eric@deptj.eu> wrote:\r
+>> On Sat, 02 Apr 2016 06:56:12 -0700, David Mazieres <dm-list-email-notmuch@scs.stanford.edu> wrote:\r
+>>> David Bremner <david@tethera.net> writes:\r
+>>> \r
+>>>> David Mazieres <dm-list-email-notmuch@scs.stanford.edu> writes:\r
+>>>>\r
+>>>>> Is there any way to break an existing thread (so as to start over with a\r
+>>>>> smaller thread), or otherwise to tweak the threading rules so that a\r
+>>>>> particular References header gets ignored.\r
+>>>>\r
+>>>> Currently there is no way to do this, as threads are "stateless"\r
+>>>> i.e. created on the fly by _notmuch_create_thread based only on\r
+>>>> immutable mail data.\r
+>>> \r
+>>> Thanks.\r
+>>> \r
+>>>>> It's annoyingly slow to open\r
+>>>>> a thread with 10,000 messages just to read one SMS. I'm almost tempted\r
+>>>>> to mangle the messages on delivery and remove the References header\r
+>>>>> before notmuch sees them, but it would be nice to have a cleaner\r
+>>>>> solution, as there are other situations in which one might want to\r
+>>>>> "reset" a really long thread.\r
+>>>>\r
+>>>> Like this thread ;).\r
+>>> \r
+>>> Oops, sorry for the irrelevant thread inclusion. I guess emacs adds the\r
+>>> References header after a message is sent is sent? In my setup, the\r
+>>> easiest way to post to a mailing list is to reply to an existing message\r
+>>> (since I subscribe to each list under a different email address). I\r
+>>> tried to start a new thread by deleting the In-Reply-To and header which\r
+>>> was all I saw, but I guess the References header got inserted later...\r
+>>\r
+>> Neither notmuch emacs nor any other email client has any business\r
+>> inserting a References header after the user "presses Send". On a new\r
+>> message it shouldn't exist unless inserted manually, and on a reply it\r
+>> should come from the replied-to message (and be changed) before you start\r
+>> "replying". More likely that (if you didn't miss it) it was not shown\r
+>> to you although it existed - that would count as a bug in my opinion\r
+>> (I don't use emacs for anything, not even notmuch).\r
+> \r
+> By default the reference header is hidden. It is controlled by\r
+> message-hidden-headers which you can customize. (Note notmuch adds\r
+> user-agent to this list via notmuch-mua-hidden-header.)\r
+\r
+Ah. Well of course I didn't know that since I don't use emacs. I guess\r
+that if the OP is going to use reply to start new threads he should\r
+unhide it.\r
+\r
+>> Actually the message you replied to has no References header, but notmuch\r
+>> reply (command line) to it generates both References and In-Reply-To\r
+>> (same content). I assume notmuch emacs does the same. I don't believe\r
+>> that References should be generated in this situation, its only use\r
+>> would be by a threading algorithm that doesn't use In-Reply-To, and I\r
+>> would consider that a bug in said algorithm.\r
+> \r
+> That isn't my reading of RFC2822 (section 3.6.4):\r
+> \r
+> The "References:" field will contain the contents of the parent's\r
+> "References:" field (if any) followed by the contents of the parent's\r
+> "Message-ID:" field (if any).\r
+\r
+OK, I guess it should be there. In which case it shouldn't default to\r
+hidden in any MUA, far too many people use the reply-for-new approach\r
+without understanding it.\r
+\r
+>> Actually I think there should be a "reply as new" option which uses\r
+>> the other message but does not add either In-Reply-To or References\r
+>> (and does not carry the latter forward if it exists).\r
+> \r
+> That would be possible. If you don't actually want to include the\r
+> message itself then "c f" to stash the from, and then pasting that as\r
+> the "to" address gets pretty close.\r
+\r
+Eric\r
+-- \r
+ms fnd in a lbry\r
projects / notmuch-archives.git / commitdiff