Bug: fatal error with notmuch new, second run starts indexing all over again
David Bremner
david at tethera.net
Sun Jul 9 07:35:27 PDT 2017
Gregor Zattler <telegraph at gmx.net> writes:
> Hi David,
> * David Bremner <david at tethera.net> [09. Jul. 2017]:
>> Gregor Zattler <telegraph at gmx.net> writes:
>>> Since its an email from an open mailing list I attach it to
>>> this very email.
>>>
>>
>> It might or might not be related, but I noticed that those two messages
>> get merged for me into a thread 1734 messages long of org-mode messages
>> (I have some old org messages, but I think I not the two you mention).
>>
>> I'm not sure yet if it's a bug in notmuch, or something strange about
>> mail from the org-mode list.
>
> This *might* be related with some other problem I reported
> regarding false threading of messages, as discussed in the thread
> containing amongst others id:874nvcekjk.fsf at qmul.ac.uk
>
> Short version: Some of the messages on this mailinglist had very
> weired References: headers mot probably causing notmuch to
> misbehave while threading the messages. But then there was no
> xapian exeption involved.
>
Right. I looks like there are indeed many message-ids in the resulting
database that look like valid email addresses. So that problem persists,
despite an attempted fix discussed in that thread.
I was wondering if the exception could result from overflowing some
internal limit due to threads many thousands of messages long. I will be
hard to know until I can replicate the exception. Perhaps a more
complete org-mode list archive would do it.
d
More information about the notmuch
mailing list