From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 1F825431FC7 for ; Mon, 27 Jan 2014 09:07:30 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ihQBnzjqxPA for ; Mon, 27 Jan 2014 09:07:22 -0800 (PST) Received: from earth.solardns.com (earth.solardns.com [94.76.229.85]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id B1939431FBF for ; Mon, 27 Jan 2014 09:07:22 -0800 (PST) Received: from cpc1-finc12-2-0-cust846.4-2.cable.virginm.net ([82.18.251.79]:47086 helo=teckel.deptj.eu) by earth.solardns.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1W7peb-0006wl-5Z for notmuch@notmuchmail.org; Mon, 27 Jan 2014 17:07:21 +0000 Received: from eric by teckel.deptj.eu with local (Exim 4.71) (envelope-from ) id 1W7pea-0006EC-IK for notmuch@notmuchmail.org; Mon, 27 Jan 2014 17:07:20 +0000 Date: Mon, 27 Jan 2014 17:07:20 +0000 Message-Id: From: Eric Subject: Re: Bug?: notmuch-search-show-thread shows several threads; only one containing matching messages To: notmuch In-Reply-To: <20140126212604.GC10844@boo.workgroup> References: <8762fzry7k.fsf@servo.finestructure.net> <20120126124450.GB30209@shi.workgroup> <87mx9avbc1.fsf@praet.org> <20120129234213.GB11460@shi.workgroup> <87zkd5655g.fsf@praet.org> <20120130190425.GB13521@shi.workgroup> <878vkoev95.fsf@qmul.ac.uk> <20120130223416.GA26239@shi.workgroup> <874nvcekjk.fsf@qmul.ac.uk> <87lhy5pko1.fsf@zancas.localnet> <20140126212604.GC10844@boo.workgroup> X--MailScanner-Information: Please contact the ISP for more information X--MailScanner-ID: 1W7peb-0006wl-5Z X--MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details X--MailScanner-SpamCheck: X--MailScanner-From: eric@deptj.eu X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - earth.solardns.com X-AntiAbuse: Original Domain - notmuchmail.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - deptj.eu X-Get-Message-Sender-Via: earth.solardns.com: authenticated_id: deptjeu/from_h X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 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, 27 Jan 2014 17:07:30 -0000 On Sun, 26 Jan 2014 22:26:04 +0100, Gregor Zattler wrote: > Hi David, > * David Bremner [24. Jan. 2014]: > > Mark Walters writes: > >> I have looked at this and I think this is not notmuch's fault: I think > >> it is a mua doing strange things: > >> > >> One of the mails has an in-reply-to header which looks like > >> > >> In-reply-to: Message from Carsten Dominik of "Tue, 15 Mar 2011 12:18:51 BST." <17242340-A14F-495A-B144-20C96D52B620@gmail.com> > >> > >> and I think notmuch is taking the carsten.dominik@gmail.com as message > >> id. > >> > > > > Can someone test if this is fixed by cf8aaafbad68 (i.e. does the problem > > persist in git master or 0.17)? > > The problem is *not* fixed. I've never been happy with notmuch's threading, always seem to get too many threads, so I tend to do notmuch show --format=mbox \ $(notmuch search --output=threads -- whatever) | mhonarc -tlevels 15 - to work out which threads I want (I am not an emacs user!). mhonarc, as far as I know, uses something like the jwz algorithm ( http://http://www.jwz.org/doc/threading.html), the use of which would solve my problem but possibly not Gregor's. If that is indeed caused by the header referred to above and there is some email client which does that, it would need special handling in jwz and probably in any algorithm, but the maintainers of the mail client should also be told to fix it! (RFC2822) Digression I know, but I just wanted to flag the need for more work in general on threading in notmuch. Eric -- ms fnd in a lbry