From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 21CFB6DE2E1B for ; Sun, 9 Jul 2017 10:10:38 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[AWL=0.010, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 18rpZqF2Xndj for ; Sun, 9 Jul 2017 10:10:37 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id DAE196DE2E1A for ; Sun, 9 Jul 2017 10:10:36 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1dUFfz-0002JC-CS; Sun, 09 Jul 2017 13:07:19 -0400 Received: (nullmailer pid 7055 invoked by uid 1000); Sun, 09 Jul 2017 17:10:33 -0000 From: David Bremner To: Gregor Zattler , notmuch Subject: Re: Bug?: notmuch-search-show-thread shows several threads; only one containing matching messages In-Reply-To: <874nvcekjk.fsf@qmul.ac.uk> References: <20120126004024.GA13704@shi.workgroup> <20120126011903.GA1176@mit.edu> <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> Date: Sun, 09 Jul 2017 14:10:33 -0300 Message-ID: <87h8yl359y.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 17:10:38 -0000 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. > > A similar in-reply-to header appears in the other thread so notmuch > pairs them up. According to http://www.jwz.org/doc/threading.html this > form of header is not allowed under RFC2822 but was allowed under the > earlier RFC822. I have identified a second, similar problem. Some MUA insert(s|ed) the From: address into the References field. For an example see id:t2sfa09ca6d1004220920haccb86aam4bb949c77024c6e6@mail.gmail.com https://www.mail-archive.com/emacs-orgmode@gnu.org/msg24266.html This seems to be another throwback to rfc822 I don't know how notmuch can detect this once it those references propagate to replies. - we could merge threads only based on messages known to exist (ignoring ghost messages), but presumably there's a reason we invented ghost messages - we could, at some point in future support blacklisting references (using message properties).