Re: Bug?: notmuch-search-show-thread shows several threads; only one containing matching messages
Mark Walterswrites: > > 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 of > "Tue, 15 Mar 2011 12:18:51 BST." > <17242340-a14f-495a-b144-20c96d52b...@gmail.com> > > and I think notmuch is taking the carsten.domi...@gmail.com as message > id. > > A similar in-reply-to header appears in the other thread so notmuch > pairs them up. According to http://www.jwz.org/doc/threading.html this > form of header is not allowed under RFC2822 but was allowed under the > earlier RFC822. I have identified a second, similar problem. Some MUA insert(s|ed) the From: address into the References field. For an example see id:t2sfa09ca6d1004220920haccb86aam4bb949c77024c...@mail.gmail.com https://www.mail-archive.com/emacs-orgmode@gnu.org/msg24266.html This seems to be another throwback to rfc822 I don't know how notmuch can detect this once it those references propagate to replies. - we could merge threads only based on messages known to exist (ignoring ghost messages), but presumably there's a reason we invented ghost messages - we could, at some point in future support blacklisting references (using message properties). ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: Bug: fatal error with notmuch new, second run starts indexing all over again
Gregor Zattlerwrites: > Hi David, > * David Bremner [09. Jul. 2017]: >> Gregor Zattler 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@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 ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: Bug: fatal error with notmuch new, second run starts indexing all over again
Hi David, * David Bremner[09. Jul. 2017]: > Gregor Zattler 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@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. Otherwise I did an extensive memory test: no prblem and an smartctl -t long and -t offline test: no problems. Remains to do a bisecting but I have no free time atm. Will report back later. Ciao, Gregor -- -... --- .-. . -.. ..--.. ...-.- ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: Bug: fatal error with notmuch new, second run starts indexing all over again
Gregor Zattlerwrites: > > 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. d ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
[PATCH] emacs: change default for notmuch-crypto-process-mime to t
There are some cases like remote usage where this might cause problems, but those users can easily customize the variable. The inconvenience seems to be outweighed by the security benefit for most users. --- emacs/notmuch-crypto.el | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/emacs/notmuch-crypto.el b/emacs/notmuch-crypto.el index 0af727ef..fc2b5301 100644 --- a/emacs/notmuch-crypto.el +++ b/emacs/notmuch-crypto.el @@ -24,7 +24,7 @@ (require 'epg) (require 'notmuch-lib) -(defcustom notmuch-crypto-process-mime nil +(defcustom notmuch-crypto-process-mime t "Should cryptographic MIME parts be processed? If this variable is non-nil signatures in multipart/signed @@ -40,6 +40,7 @@ providing a prefix when viewing a signed or encrypted message, or by providing a prefix when reloading the message in notmuch-show mode." :type 'boolean + :package-version '(notmuch . "0.25") :group 'notmuch-crypto) (defface notmuch-crypto-part-header -- 2.13.2 ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch