From: David Bremner <david@tethera.net>
To: Gregor Zattler <telegraph@gmx.net>, notmuch <notmuch@notmuchmail.org>
Subject: Re: Bug?: notmuch-search-show-thread shows several threads; only one
	containing matching messages
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>
User-Agent: Notmuch/0.17+49~gaa57e9d (http://notmuchmail.org) Emacs/24.3.1
	(x86_64-pc-linux-gnu)
Date: Sun, 26 Jan 2014 19:43:47 -0400
Message-ID: <87r47ul364.fsf@zancas.localnet>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list

Gregor Zattler <telegraph@gmx.net> writes:

> Today I produced another mbox with the very same command but with
> a now larger email corpus freshly indexed with a fresh notmuch.
> The mbox contains (according to mutt) 507 messages in 34 threads.
> One of them is the thread I searched for.
>
> I grepped for the 7 subjects within the 34 subjects and only 5
> showed up.

I don't know what you mean here. Grepped where? in the raw messages?

> If somebody want's to dig into this: I can provide the two
> mboxes. 
>
> Disclaimer: Many of the emails which arrived before the problem
> report are not the exact same than then, because since the I
> mangled them with a script.  This should have not changed the
> threading but I cannot be 100% sure.  But if it's important for
> further investigation I'm probably able to reproduce the status
> quo of the email corpus then from my backups.

If it's currently not working then I guess your current corpus should be
fine. It would probably help to restate what exactly is wrong. There was
a lot of discussion, and the concrete problem I saw identified (in
id:874nvcekjk.fsf@qmul.ac.uk ) was that certain malformed In-reply-to
headers were causing unrelated threads to merge.

d