From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id E80266DE0203 for ; Sat, 21 Jul 2018 10:36:16 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.493 X-Spam-Level: X-Spam-Status: No, score=-0.493 tagged_above=-999 required=5 tests=[AWL=0.217, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SF9XqJj4O_-b for ; Sat, 21 Jul 2018 10:36:15 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by arlo.cworth.org (Postfix) with ESMTPS id 363E56DE01E7 for ; Sat, 21 Jul 2018 10:36:14 -0700 (PDT) Received: from len.workgroup ([84.185.108.99]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LkCU2-1gHuF61Eks-00cBTF for ; Sat, 21 Jul 2018 19:36:10 +0200 From: Gregor Zattler To: notmuch@notmuchmail.org Subject: Re: v1: fix for threading of replies to ghost messages In-Reply-To: <20180720233746.2844-1-david@tethera.net> References: <20180720233746.2844-1-david@tethera.net> Mail-Followup-To: notmuch@notmuchmail.org Date: Sat, 21 Jul 2018 19:35:37 +0200 Message-ID: <871sbwbifq.fsf@len.workgroup> MIME-Version: 1.0 Content-Type: text/plain X-Provags-ID: V03:K1:/YJxiTMdKI/X3uBMo6ytVUhG1ALYQpq+PQuZCsSEnT3XsMoz0EZ mFC/eJZMkOFm6+ZQdb3t1drNfoNGe9xdZIcAEWyUkdtz1nwScv18RFq7i0VV8kaxZIUXR2D 3U9Ihww6rTZWcYC5OE8xFvg5h8uAKrXGEJjwdmbO83Fg0C3hys8bFCVZAlbmVKMivtnDDY7 5TkikEWycqon/86fHB/+A== X-UI-Out-Filterresults: notjunk:1;V01:K0:pOg/hL3uut0=:SJNcPH4m2cOBhuCKDDT3io J8xcGSicYrDWgHeTJ/QqubpoopIUEY6Ck6m9EPOQmHRQNLopfEmRLLL2SMDPkTiHgHpraEb+V 2M0r7lkrYA73EJcmOEOKLXguXCtVfY5FwIaZojHHx8afPWgrdqUut03cQd0Fm1hfMXXNlMiLq R8fNKlaxOTFjv3DJeO5UZxnVYoKcQ7igg29Kioylowuzsv6X8TDIwQQYJ5sTzojyFGhKXAdbw sbYCLabty2a0iqFXrGxLNwNOADp+kIx2//JxBMRChG7oWy9SdjuUy0H1iz6tMwmvTOjy6y1gW SDEPVuAPGhFAyS7H9Ve99DQEBfmwfxKVVruiVpGVN77+V3Upq2qwMzHvDTHEi1TuJmnlaBJFc lpN1rUUkl69jpI+HLcTZQQrxEf0XY7488Zfb6h5qsXVqGHiOnH1FlVa4m8cKAcxIR3NHRFUfC LquoeCrZAHMIfNGjrQldV7J8cWz9tMI/0f//FkeFIR7VOTXvYWU2NPTehUROAWFJB5/wJF2FW iZdyReirXIzSaKNut4LB5IYHdw4INBDEiLI2/LcCbHqUEh4aKKeEdhISNLaCtml0fdzSHGjW1 EqgxdnSdV5R+NWvKqEYvMr2qzaHFbGjUd/d3ZmyxMYNy9iry6uNSx6TvYBQApg23XjURPb2s0 nml50tBrIdFISDO7sixt33eNDBGY4unhZqAvLaCDmoMAYJNeJtZBGzDwyPSdcpIrvLKOlBBi6 jOLsYggYWsgGGzSVM3wBVYUViM06BHSueYms53YsNoeLYZjIrsgEuJTd+hbWXc1wV3YaLmAOM BE0mFoK X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jul 2018 17:36:17 -0000 Hi David, * David Bremner [2018-07-21; 08:37]: > See the thread at id:87efgmmysi.fsf@len.workgroup for discussion. > > This series finally bites the bullet and uses the References header > for threading. > > Please test this series, there are lots of tricky cases with threading. I applied the patches and looked with notmuch-emacs for threads which before would probably show wrong ordering of messages. The half a dozen threads were all shown in the correct order with respect to parents and children, but I found from those not disclosable RT ticket mails (I mentioned in above referenced thread): - Threads where the "Resolved" message was shown first but it's References: header contains only a fake Message-Id: (which is strange: why does notmuch show this resolved-mail in this thread?). - one thread where two children of one message were shown with correct (meaning: same) indentation but the older one before (over) the newer one. I'll ask if I may disclose this threads if this it would be helpful for diagnosis. Thanks for your attention and work regarding my problem report with notmuch. Ciao; Gregor