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 912E4429E36 for ; Wed, 25 Jan 2012 17:19:42 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] 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 BDlmMbvLSaEp for ; Wed, 25 Jan 2012 17:19:42 -0800 (PST) Received: from dmz-mailsec-scanner-8.mit.edu (DMZ-MAILSEC-SCANNER-8.MIT.EDU [18.7.68.37]) by olra.theworths.org (Postfix) with ESMTP id 130C5431FBC for ; Wed, 25 Jan 2012 17:19:42 -0800 (PST) X-AuditID: 12074425-b7f4a6d0000008e0-eb-4f20aa2d9af5 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 17.2A.02272.D2AA02F4; Wed, 25 Jan 2012 20:19:41 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id q0Q1JeqP012136 for ; Wed, 25 Jan 2012 20:19:41 -0500 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91]) (authenticated bits=0) (User authenticated as amdragon@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q0Q1JdRB000380 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for ; Wed, 25 Jan 2012 20:19:40 -0500 (EST) Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77) (envelope-from ) id 1RqDzT-0000SX-5t for notmuch@notmuchmail.org; Wed, 25 Jan 2012 20:19:03 -0500 Date: Wed, 25 Jan 2012 20:19:03 -0500 From: Austin Clements To: notmuch Subject: Re: [Emacs] Bug?: notmuch-search-show-thread shows several threads; only one containing matching messages Message-ID: <20120126011903.GA1176@mit.edu> References: <20120126004024.GA13704@shi.workgroup> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120126004024.GA13704@shi.workgroup> User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDIsWRmVeSWpSXmKPExsUixCmqrKu7SsHf4PkEJYvrN2cyOzB6PFt1 izmAMYrLJiU1J7MstUjfLoEr4+PhxUwFj7gqXu+7ytrAeIGji5GTQ0LAROLt1XNsELaYxIV7 64FsLg4hgX2MEo/nPmCCcM4xSjxZtJwdwnnOJPHqxUewFiGBQ4wSV/fxg9gsAqoSH49NYQSx 2QQ0JLbtXw5miwDFN629C2YLC5RILN7yiBXE5hXQlti9cgnQUA6gOUYSD08pQ4QFJU7OfMIC YjMLaEnc+PeSCaSEWUBaYvk/sKM5BYwlVrUtBpsoKqAiMeXkNrYJjIKzkHTPQtI9C6F7ASPz KkbZlNwq3dzEzJzi1GTd4uTEvLzUIl0LvdzMEr3UlNJNjKBAZXdR3cE44ZDSIUYBDkYlHt4k AwV/IdbEsuLK3EOMkhxMSqK8U5cDhfiS8lMqMxKLM+KLSnNSi4GhwcGsJMIrZg+U401JrKxK LcqHSUlzsCiJ82pqvfMTEkhPLEnNTk0tSC2CycpwcChJ8DavBGoULEpNT61Iy8wpQUgzcXCC DOcBGl4FUsNbXJCYW5yZDpE/xagoJc7rC5IQAElklObB9cISyStGcaBXhHlTQKp4gEkIrvsV 0GAmoMFLdeVBBpckIqSkGhg7OCQVpil7vArK2cJ0afuqT5xMM9cZfK75+PL7wmiG5ox1aekT M1m5t56tPD75h7Lavuobsu4HHql6+n+YJjL35w3JJOZPR+zkBD/tf7/5M2PXnNJmM8nIZ0uO sp8UuOJh8/ORlzJT2lnzrzGnZu14E9x76o7W/Zlr7309JfJctizvm/0xz8tPlFiKMxINtZiL ihMBPXapHv8CAAA= 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: Thu, 26 Jan 2012 01:19:42 -0000 Quoth Gregor Zattler on Jan 26 at 1:40 am: > [sorry for the long and meandering explanation, I do not know how > to express the issue more concise] > > Dear notmuch developers, > > may someone please enlighten me regarding this behaviour: > > I experienced a situation where the Emacs interface shows three > (3) different threads in one notmuch show buffer. I thought it > should show only one. Perhaps this is the result of notmuch show > showing messages which do not match the search pattern and do not > belong to one thread which contains messages which do so.[1] It's always possible that this is a bug, but one potential legitimate cause comes to mind. If *any* of the messages in each of the apparently unrelated threads contain a message ID of any of the messages in the original thread (or one of the other unrelated threads) in their References or In-reply-to headers, notmuch will merge the threads and cause the exact behavior you're seeing. One very common cause of this is someone using "reply" to get an initial set of recipients, but then replacing the entire message and subject (presumably without realizing that the mail is still tracking what it was a reply to). This can also happen if someone intentionally replies to multiple messages (though few mail clients support this), or if there was a message ID collision.