From: Gregor Zattler <telegraph@gmx.net>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: Bug?: notmuch-search-show-thread shows several threads; only one containing matching messages
Date: Sun, 26 Jan 2014 22:26:04 +0100 [thread overview]
Message-ID: <20140126212604.GC10844@boo.workgroup> (raw)
In-Reply-To: <87lhy5pko1.fsf@zancas.localnet>
Hi David,
* David Bremner <david@tethera.net> [24. Jan. 2014]:
> Mark Walters <markwalters1009@gmail.com> 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 <carsten.dominik@gmail.com> 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.
>>
>
> Can someone test if this is fixed by cf8aaafbad68 (i.e. does the problem
> persist in git master or 0.17)?
The problem is *not* fixed.
I was the one who reported this problem two years ago. I did the
same notmuch search again. Since I did no know if it's important
with which version the emails were indexed I did a full index
with notmuch 0.17+40~gecbb29e.
I still have the mbox produced with notmuch show two years ago.
Viewed with mutt (1) I see 206 messages in 7 threads (number of
lines after collapse-all) (notmuch emacs show showed three
threads then). One of the threads is the one I searched for.
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.
Only 17 of the 507 messages arrived since the problem report two
years ago.
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.
Thanks for your persistence.
Ciao, Gregor
--
-... --- .-. . -.. ..--.. ...-.-
next prev parent reply other threads:[~2014-01-26 21:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 0:40 [Emacs] Bug?: notmuch-search-show-thread shows several threads; only one containing matching messages Gregor Zattler
2012-01-26 1:19 ` Austin Clements
2012-01-26 2:31 ` Jameson Graef Rollins
2012-01-26 12:44 ` Gregor Zattler
2012-01-26 13:16 ` Jani Nikula
2012-01-29 23:36 ` Gregor Zattler
2012-01-26 13:32 ` Pieter Praet
2012-01-29 23:42 ` Gregor Zattler
2012-01-30 7:06 ` Pieter Praet
2012-01-30 19:04 ` Gregor Zattler
2012-01-30 21:27 ` Mark Walters
2012-01-30 22:34 ` Gregor Zattler
2012-01-31 1:18 ` Mark Walters
2012-01-31 16:31 ` Jameson Graef Rollins
2014-01-24 13:35 ` David Bremner
2014-01-26 21:26 ` Gregor Zattler [this message]
2014-01-26 23:43 ` David Bremner
2014-01-27 1:48 ` Gregor Zattler
2014-02-17 0:16 ` David Bremner
2014-01-27 17:07 ` Eric
2017-07-09 17:10 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140126212604.GC10844@boo.workgroup \
--to=telegraph@gmx.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).