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 025D06DE01F0 for ; Thu, 28 Jun 2018 04:24:13 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[AWL=0.000, RCVD_IN_DNSWL_LOW=-0.7] 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 wT5Tkr_QOPa6 for ; Thu, 28 Jun 2018 04:24:12 -0700 (PDT) X-Greylist: delayed 2876 seconds by postgrey-1.36 at arlo; Thu, 28 Jun 2018 04:24:12 PDT Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) by arlo.cworth.org (Postfix) with ESMTPS id 156B46DE01CE for ; Thu, 28 Jun 2018 04:24:11 -0700 (PDT) Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w5SAXs7a145047 for ; Thu, 28 Jun 2018 06:36:13 -0400 Received: from e06smtp05.uk.ibm.com (e06smtp05.uk.ibm.com [195.75.94.101]) by mx0b-001b2d01.pphosted.com with ESMTP id 2jvw40ajwn-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 28 Jun 2018 06:36:13 -0400 Received: from localhost by e06smtp05.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 28 Jun 2018 11:36:11 +0100 Received: from b06cxnps4076.portsmouth.uk.ibm.com (9.149.109.198) by e06smtp05.uk.ibm.com (192.168.101.135) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Thu, 28 Jun 2018 11:36:09 +0100 Received: from d06av22.portsmouth.uk.ibm.com (d06av22.portsmouth.uk.ibm.com [9.149.105.58]) by b06cxnps4076.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w5SAa8wo25690294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 28 Jun 2018 10:36:08 GMT Received: from d06av22.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C6CBC4C04A; Thu, 28 Jun 2018 11:35:57 +0100 (BST) Received: from d06av22.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 782FA4C050; Thu, 28 Jun 2018 11:35:57 +0100 (BST) Received: from localhost (unknown [9.124.35.23]) by d06av22.portsmouth.uk.ibm.com (Postfix) with ESMTP; Thu, 28 Jun 2018 11:35:57 +0100 (BST) Date: Thu, 28 Jun 2018 16:06:05 +0530 From: "Naveen N. Rao" Subject: Re: 'notmuch search thread:<>' lists multiple threads To: David Bremner , notmuch@notmuchmail.org References: <1523007700.l8xm6nm6af.naveen@linux.ibm.com> <87sh86v1oc.fsf@tethera.net> <878t9wvbmu.fsf@tethera.net> <1524045467.a0aq8zermb.naveen@linux.ibm.com> <87r2n8m5ky.fsf@tethera.net> In-Reply-To: <87r2n8m5ky.fsf@tethera.net> User-Agent: astroid/0.11.1 (https://github.com/astroidmail/astroid) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-TM-AS-GCONF: 00 x-cbid: 18062810-0020-0000-0000-0000029FE6EA X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18062810-0021-0000-0000-000020EC6AC1 Message-Id: <1530181883.fliclpetue.naveen@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-06-28_05:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1806210000 definitions=main-1806280122 X-Mailman-Approved-At: Thu, 28 Jun 2018 05:52:48 -0700 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: Thu, 28 Jun 2018 11:24:13 -0000 Hi David, David Bremner wrote: > "Naveen N. Rao" writes: >=20 >> In my case, I seem to be having the In-Reply-To headers. I end up with=20 >> two files per message: one from my inbox and one from the gmane archive=20 >> that I pull in. All the messages from the gmane archive seem to have a=20 >> re-written 'In-Reply-To' header, but 'Message-Id' and 'References' are=20 >> the same. >=20 > That sounds like essentially the same issue, due to the fact that > notmuch prefers In-Reply-To when choosing a parent for a message. >=20 > Currently the database is correct (or at least one not-crazy definition > of correct): all of the reference and in-reply-to terms are attached to > the message document in the database. On the other hand, the in memory > data structures currently assume that In-reply-to is a unique value > (with ties broken at indexing time). >=20 > It might be that the solution is to read a list of in-reply-to values > and use all of them in threading. At a quick glance, that looks doable; > I'm just not sure about unintended consequences. Were you able to look into this again? Using a list of in-reply-to values sounds like a good option, though I=20 clearly have no idea about other consequences from that. If you have a=20 patch, I can help test that. Thanks, Naveen =