Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 1B0C06DE02DD for ; Mon, 4 Apr 2016 06:00:43 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.816 X-Spam-Level: X-Spam-Status: No, score=-0.816 tagged_above=-999 required=5 tests=[AWL=-0.246, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id INhsCxW6E1Jo for ; Mon, 4 Apr 2016 06:00:32 -0700 (PDT) Received: from mail-lb0-f194.google.com (mail-lb0-f194.google.com [209.85.217.194]) by arlo.cworth.org (Postfix) with ESMTPS id 5E66E6DE02C9 for ; Mon, 4 Apr 2016 06:00:32 -0700 (PDT) Received: by mail-lb0-f194.google.com with SMTP id q4so22220268lbq.3 for ; Mon, 04 Apr 2016 06:00:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:in-reply-to:references:user-agent:date:message-id :mime-version; bh=bcw0X3bZpCLGj3a9JBEr526g6MMoKIV8DhbxnjA9Ids=; b=AglQwbe8svd19riP93ftrkcPKw2M0mxZoXnkPi6Kr1rwxP26+oSVcO81FEdXD/fZXD Q2ODWd4UeW2M6cgEGAlR+iVA4N3pdSkKWO9BNd9NRqf7eVZ/RlvcGjkGu9JfhEuSmgqp +a304pHCGj1DOVjWhaQLSnmFwcEx4f2AVyCx3cm7dwlpfVZpneOLfp8aHSVy/IUfiUm4 /paWSkKPOiMXYy82lKioGs47YjBCFV2gDH5yZ0x0bnRg2Ak8htpd97GRPISEcITjSQbQ Ar63DjaHBkwUsvDrIle2paJa8UL5XQI9z7PiLxc6l5DdBZku0Vx6x1CbOCeu5vhZfohf 1fkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:in-reply-to:references :user-agent:date:message-id:mime-version; bh=bcw0X3bZpCLGj3a9JBEr526g6MMoKIV8DhbxnjA9Ids=; b=j6y7peqP/4+QyA+6cD37KqXCBMxAR9zIe2TNZD+N17ChJsnY0gTH2H2F9sYhR5wZRH ldWhIKcUMhwqZKo1HJ3ul2DWdHhNwOR8CdVTSC72fd5O9tzx5JcwBvlaveuk6ijabQ5L DLn5qq1ktXzTe9mR0J8RlmlfVoSiUAmzyszvQRl7RTGWVQmx8n2A4b4nWISMED7lF8Fp 4eU6tj9+pHn8WloT8R7lXsLfO1EnMqpOatEvUkH5I0T6p2RoVcJ8kU4jGi0eZuzm/B13 cZVghsptnPHsioXQEBahId1qe9b/4s5ZZcviD6GTAZe72et3363tMewCput2WHbSgG5l qI8w== X-Gm-Message-State: AD7BkJLcAryyaBvL8mIKXWS4QR8uVXCEnmJM05aEYsuhjWu2E/PbtFN7SUjxdH1BlGYAgw== X-Received: by 10.28.125.2 with SMTP id y2mr11973639wmc.90.1459774829031; Mon, 04 Apr 2016 06:00:29 -0700 (PDT) Received: from localhost (188.29.78.141.threembb.co.uk. [188.29.78.141]) by smtp.gmail.com with ESMTPSA id u4sm29000209wjz.4.2016.04.04.06.00.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 Apr 2016 06:00:28 -0700 (PDT) From: Mark Walters To: Eric , notmuch@notmuchmail.org Subject: Re: Breaking a really long thread In-Reply-To: References: User-Agent: Notmuch/0.18.1+485~gca076ce (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Mon, 04 Apr 2016 14:00:26 +0100 Message-ID: <87k2kd8r6d.fsf@qmul.ac.uk> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 13:00:43 -0000 On Mon, 04 Apr 2016, Eric wrote: > On Sat, 02 Apr 2016 06:56:12 -0700, David Mazieres wrote: >> David Bremner writes: >> >>> David Mazieres writes: >>> >>>> Is there any way to break an existing thread (so as to start over with a >>>> smaller thread), or otherwise to tweak the threading rules so that a >>>> particular References header gets ignored. >>> >>> Currently there is no way to do this, as threads are "stateless" >>> i.e. created on the fly by _notmuch_create_thread based only on >>> immutable mail data. >> >> Thanks. >> >>>> It's annoyingly slow to open >>>> a thread with 10,000 messages just to read one SMS. I'm almost tempted >>>> to mangle the messages on delivery and remove the References header >>>> before notmuch sees them, but it would be nice to have a cleaner >>>> solution, as there are other situations in which one might want to >>>> "reset" a really long thread. >>> >>> Like this thread ;). >> >> Oops, sorry for the irrelevant thread inclusion. I guess emacs adds the >> References header after a message is sent is sent? In my setup, the >> easiest way to post to a mailing list is to reply to an existing message >> (since I subscribe to each list under a different email address). I >> tried to start a new thread by deleting the In-Reply-To and header which >> was all I saw, but I guess the References header got inserted later... > > Neither notmuch emacs nor any other email client has any business > inserting a References header after the user "presses Send". On a new > message it shouldn't exist unless inserted manually, and on a reply it > should come from the replied-to message (and be changed) before you start > "replying". More likely that (if you didn't miss it) it was not shown > to you although it existed - that would count as a bug in my opinion > (I don't use emacs for anything, not even notmuch). By default the reference header is hidden. It is controlled by message-hidden-headers which you can customize. (Note notmuch adds user-agent to this list via notmuch-mua-hidden-header.) > Actually the message you replied to has no References header, but notmuch > reply (command line) to it generates both References and In-Reply-To > (same content). I assume notmuch emacs does the same. I don't believe > that References should be generated in this situation, its only use > would be by a threading algorithm that doesn't use In-Reply-To, and I > would consider that a bug in said algorithm. That isn't my reading of RFC2822 (section 3.6.4): The "References:" field will contain the contents of the parent's "References:" field (if any) followed by the contents of the parent's "Message-ID:" field (if any). > Actually I think there should be a "reply as new" option which uses > the other message but does not add either In-Reply-To or References > (and does not carry the latter forward if it exists). That would be possible. If you don't actually want to include the message itself then "c f" to stash the from, and then pasting that as the "to" address gets pretty close. Best wishes Mark