--- /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 2B439421192\r
+ for <notmuch@notmuchmail.org>; Mon, 30 Jan 2012 13:26:33 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.098\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5\r
+ tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,\r
+ NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_MED=-2.3] 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 US4d6BVvx2FI for <notmuch@notmuchmail.org>;\r
+ Mon, 30 Jan 2012 13:26:31 -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 DCCBA431FBC\r
+ for <notmuch@notmuchmail.org>; Mon, 30 Jan 2012 13:26:30 -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 1Rryk8-0007z7-UF; Mon, 30 Jan 2012 21:26:29 +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 1Rryk8-00015m-KA; Mon, 30 Jan 2012 21:26:28 +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: <20120130190425.GB13521@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>\r
+User-Agent: Notmuch/0.11+137~g98adc3d (http://notmuchmail.org) Emacs/23.2.1\r
+ (i486-pc-linux-gnu)\r
+Date: Mon, 30 Jan 2012 21:27:34 +0000\r
+Message-ID: <878vkoev95.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: 01303b7771349fd76f80b9a195b5fd3a (of first 20000 bytes)\r
+X-SpamAssassin-Score: -1.8\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.8 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
+ * 0.5 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: Mon, 30 Jan 2012 21:26:33 -0000\r
+\r
+\r
+On Mon, 30 Jan 2012 20:04:25 +0100, Gregor Zattler <telegraph@gmx.net> wrote:\r
+> Hi Pieter,\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
+> >>> On Thu, 26 Jan 2012 13:44:50 +0100, Gregor Zattler <telegraph@gmx.net> wrote:\r
+> >>>> |> [2] grep -I "^Message-Id:" /tmp/thread-I-m-interested-in.mbox |sed -e "s/Message-Id: <//I" -e "s/>$//" >really.mid\r
+> >>>> |> grep -I -F really.mid rest.mbox\r
+> >>>> |> --> no match\r
+> >>> \r
+> [...]\r
+> >>> Also, the '-F' option expects input on stdin, not a filename.\r
+> >> \r
+> >> No, this is -F instead of -f and means --fixed-strings.\r
+> >> \r
+> > And as I said, `-F' requires input on stdin, like this:\r
+> > \r
+> > `grep -F "$(cat really.mid)" rest.mbox'\r
+> > \r
+> > Otherwise [1] you're grepping for the pattern 'really.mid' instead of\r
+> > for the patterns specified *in* 'really.mid', so naturally, you aren't\r
+> > getting any results.\r
+> \r
+> *blush* you're right and I'm wrong. I re-re-did the greps with\r
+> with the same results (no hits at all).\r
+> \r
+> [...]\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
+Hi\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
+As far as I can see your grep tests haven't checked for that. \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
+Thanks\r
+\r
+Mark\r
projects / notmuch-archives.git / commitdiff