--- /dev/null
+Return-Path: <m.walters@qmul.ac.uk>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id BF35A429E34\r
+ for <notmuch@notmuchmail.org>; Mon, 30 Jan 2012 17:17:54 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 1.401\r
+X-Spam-Level: *\r
+X-Spam-Status: No, score=1.401 tagged_above=-999 required=5\r
+ tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,\r
+ FREEMAIL_REPLY=2.499, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_MED=-2.3]\r
+ autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id jZPRLSYy+bu2 for <notmuch@notmuchmail.org>;\r
+ Mon, 30 Jan 2012 17:17:54 -0800 (PST)\r
+Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])\r
+ (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id C1E5A431FBC\r
+ for <notmuch@notmuchmail.org>; Mon, 30 Jan 2012 17:17:53 -0800 (PST)\r
+Received: from smtp.qmul.ac.uk ([138.37.6.40])\r
+ by mail2.qmul.ac.uk with esmtp (Exim 4.71)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1Rs2M1-0008HJ-Rb; Tue, 31 Jan 2012 01:17:50 +0000\r
+Received: from 94-192-233-223.zone6.bethere.co.uk ([94.192.233.223]\r
+ helo=localhost)\r
+ by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1Rs2M1-0005Rc-E1; Tue, 31 Jan 2012 01:17:49 +0000\r
+From: Mark Walters <markwalters1009@gmail.com>\r
+To: Gregor Zattler <telegraph@gmx.net>, notmuch <notmuch@notmuchmail.org>\r
+Subject: Re: Bug?: notmuch-search-show-thread shows several threads;\r
+ only one containing matching messages\r
+In-Reply-To: <20120130223416.GA26239@shi.workgroup>\r
+References: <20120126004024.GA13704@shi.workgroup>\r
+ <20120126011903.GA1176@mit.edu>\r
+ <8762fzry7k.fsf@servo.finestructure.net>\r
+ <20120126124450.GB30209@shi.workgroup> <87mx9avbc1.fsf@praet.org>\r
+ <20120129234213.GB11460@shi.workgroup> <87zkd5655g.fsf@praet.org>\r
+ <20120130190425.GB13521@shi.workgroup> <878vkoev95.fsf@qmul.ac.uk>\r
+ <20120130223416.GA26239@shi.workgroup>\r
+User-Agent: Notmuch/0.11+137~g98adc3d (http://notmuchmail.org) Emacs/23.2.1\r
+ (i486-pc-linux-gnu)\r
+Date: Tue, 31 Jan 2012 01:18:55 +0000\r
+Message-ID: <874nvcekjk.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-Sender-Host-Address: 94.192.233.223\r
+X-QM-SPAM-Info: Sender has good ham record. :)\r
+X-QM-Body-MD5: 6919f6b6598f2a54f2db22f0a2fb9248 (of first 20000 bytes)\r
+X-SpamAssassin-Score: -1.2\r
+X-SpamAssassin-SpamBar: -\r
+X-SpamAssassin-Report: The QM spam filters have analysed this message to\r
+ determine if it is\r
+ spam. We require at least 5.0 points to mark a message as spam.\r
+ This message scored -1.2 points.\r
+ Summary of the scoring: \r
+ * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/,\r
+ * medium trust\r
+ * [138.37.6.40 listed in list.dnswl.org]\r
+ * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail\r
+ provider * (markwalters1009[at]gmail.com)\r
+ * -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay\r
+ * domain\r
+ * 1.0 FREEMAIL_REPLY From and body contain different freemails\r
+ * 0.1 AWL AWL: From: address is in the auto white-list\r
+X-QM-Scan-Virus: ClamAV says the message is clean\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://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: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 31 Jan 2012 01:17:54 -0000\r
+\r
+On Mon, 30 Jan 2012 23:34:16 +0100, Gregor Zattler <telegraph@gmx.net> wrote:\r
+> Hi Mark,\r
+> * Mark Walters <markwalters1009@gmail.com> [30. Jan. 2012]:\r
+> > On Mon, 30 Jan 2012 20:04:25 +0100, Gregor Zattler <telegraph@gmx.net> wrote:\r
+> >> * Pieter Praet <pieter@praet.org> [30. Jan. 2012]:\r
+> >>> On Mon, 30 Jan 2012 00:42:14 +0100, Gregor Zattler <telegraph@gmx.net> wrote:\r
+> >>>> * Pieter Praet <pieter@praet.org> [26. Jan. 2012]:\r
+> >>>>> Here's another couple of threads squashed into a single one:\r
+> >>>>> - [O] [Use Question] Capture and long lines\r
+> >>>>> - id:"BANLkTikoF4tXuNLLufRzNSD6k2ZYs7sUcg@mail.gmail.com"\r
+> >>>>> - [O] Worg update\r
+> >>>>> - id:"m1wrfiz3ch.fsf@tsdye.com"\r
+> >>>>> - [O] Table formula to convert hex to dec\r
+> >>>>> - id:"20110724080054.GB16388@x201"\r
+> >>>>> - [O] ICS import?\r
+> >>>>> - id:"20120125173421.GQ3747@x201"\r
+> >>>>> \r
+> >>>>> \r
+> >>>>> AFAICT, none of them share Message-Id's...\r
+> >>>> \r
+> >>>> Do you consider this a bug?\r
+> >>>> \r
+> >>> \r
+> >>> I do. No idea what causes it or how to fix it though... :)\r
+> >> \r
+> >> First I thougt it' not a severe bug since one see's more not less\r
+> >> messages in notmuch show buffer. But later I realised one also\r
+> >> sees less not more threads in notmuch search buffer and might not\r
+> >> read certain notmuch threads because of "wrong" $Subject: in\r
+> >> notmuch search buffer.\r
+> \r
+> > I think notmuch links two messages into the same thread if they have an\r
+> > in-reply-to or reference header in common: i.e the messages reference a\r
+> > common parent message. (See comment in lib/database.cc "Even before a\r
+> > message is added, it's pre-allocated thread ID is useful so that all\r
+> > descendant messages that reference this common parent can be recognized\r
+> > as belonging to the same thread.")\r
+> \r
+> So in case message a from thread A and message b from B would\r
+> name the same Message c in their In-Reoply-To:/References:\r
+> headers, while c is not (for some reason) in A or B, notmuch\r
+> would assume both threads linked? Makes sense.\r
+> \r
+> > As far as I can see your grep tests haven't checked for that. \r
+> \r
+> True.\r
+> \r
+> > Also, could you email me the mbox you had (I think you said that it was\r
+> > a mailing list so all public) and I will take a look?\r
+> \r
+> Sure, I do so off-list because of the size of the attachment.\r
+\r
+Hi \r
+\r
+I have looked at this and I think this is not notmuch's fault: I think\r
+it is a mua doing strange things:\r
+\r
+One of the mails has an in-reply-to header which looks like\r
+\r
+In-reply-to: Message from Carsten Dominik <carsten.dominik@gmail.com> of "Tue, 15 Mar 2011 12:18:51 BST." <17242340-A14F-495A-B144-20C96D52B620@gmail.com>\r
+\r
+and I think notmuch is taking the carsten.dominik@gmail.com as message\r
+id.\r
+\r
+A similar in-reply-to header appears in the other thread so notmuch\r
+pairs them up. According to http://www.jwz.org/doc/threading.html this\r
+form of header is not allowed under RFC2822 but was allowed under the\r
+earlier RFC822.\r
+\r
+You can see several such messages on the gnu-mailing list site eg\r
+\r
+ftp://lists.gnu.org/emacs-orgmode/2011-11 \r
+\r
+search for "in-reply-to: M" but they all appear to be from the same\r
+person (running mh-e 8.3 nmh under emacs 24)\r
+\r
+In my collection from the linux kernel mailing list I get some examples\r
+of in-reply-to not just being : <msg-id> but it was only about 200 from\r
+100,000 messages in the second half of 2010 (the most recent archives I\r
+have).\r
+\r
+Best wishes\r
+\r
+Mark\r
+\r
+\r
+\r
+\r
projects / notmuch-archives.git / commitdiff