Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n98i2-00079H-GC for pgsql-www@arkaria.postgresql.org; Sun, 16 Jan 2022 16:48:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n98i0-0003ZG-HJ for pgsql-www@arkaria.postgresql.org; Sun, 16 Jan 2022 16:48:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n98hz-0003Z7-Vv for pgsql-www@lists.postgresql.org; Sun, 16 Jan 2022 16:48:48 +0000 Received: from anastigmatix.net ([68.171.219.55]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n98hx-0006Fv-6s for pgsql-www@postgresql.org; Sun, 16 Jan 2022 16:48:46 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=anastigmatix.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=YXb5+sNiZ0XIBwq/yI74bCFpl7kewhRpiee9cQ8epqU=; b=nSDsnLgu78oamBRBHhN7RrvsKA CYROKyqvOmdfsm9JryC8R+1/6P20URkP01WBRBe9D8XoZ3u9QbbDF4wCvccmHlkUKMmvjwM+SXjrs iJJqR/9wiDNkZlGZaioGuVe+5vB+iuVKIp7KQQLRwmloS2sARo96TdyEylPEQaq8IHlva8uToNs5Y 37lHMScBokPrtTdnbkRNGC0R5dUZrhZvqXwedsGRHijcgdvfCIR5DBCaHTzUkCScwnPJFwjXx3lab kdpmXF13iF5dLEibTOWklIKs8u3UxjqHWDF6foV3xiVN8LNWs3k3fc2t32p0jqXrgjQp9j0lNj3b1 Yii60YWQ==; Received: from 50-102-16-206.prtg.in.frontiernet.net ([50.102.16.206]:49917) by bay.acenet.us with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1n98hu-009l7e-Qe; Sun, 16 Jan 2022 11:48:43 -0500 Subject: Re: missing ML messages To: Magnus Hagander , Justin Pryzby References: <20210123025941.GA30285@telsasoft.com> <1287447.1611371258@sss.pgh.pa.us> <20210123031431.GI27167@telsasoft.com> <20220109193535.GM14051@telsasoft.com> Cc: pgsql-www@postgresql.org From: Chapman Flack Message-ID: <61E44C69.4050302@anastigmatix.net> Date: Sun, 16 Jan 2022 11:48:41 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bay.acenet.us X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - anastigmatix.net X-Get-Message-Sender-Via: bay.acenet.us: authenticated_id: chap@anastigmatix.net X-Authenticated-Sender: bay.acenet.us: chap@anastigmatix.net X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 01/16/22 11:34, Magnus Hagander wrote: >> https://www.postgresql.org/message-id/61C09C1D.5050702@anastigmatix.net >>> *seeing that RFC 5322 3.6.4 permits more than one msg-id for in-reply-to, >>> crosses fingers to see what PGLister will make of it* > > A first step would probably be to figure out *what* to do. The RFC > basically appears to punt on the whole idea of what to do with > multiple parents. I'm unsure what would be the best thing for pglister > to do. Just pick the first entry and go with that? That would > certainly be the easiest, but would it be correct? I'm not sure whether the best metric is 'correct' or 'useful'. I think that on the one occasion where I jumped through the hoops of making my MUA produce a message with two in-reply-to IDs, it was in the hope that might allow future readers of either archive thread to find the message. Regards, -Chap