public inbox for [email protected]
help / color / mirror / Atom feedFrom: Chapman Flack <[email protected]>
To: Magnus Hagander <[email protected]>
To: Justin Pryzby <[email protected]>
Cc: [email protected]
Subject: Re: missing ML messages
Date: Sun, 16 Jan 2022 11:48:41 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CABUevEzYdfJ1pvreTM77xspNpnf5qko-_aMoLh+kC7Wdz6Gz6g@mail.gmail.com>
References: <[email protected]>
<[email protected]>
<[email protected]>
<CABUevEyYop_zjaCggv-FNd9HCRyb4D2xmj5+Wf16Xqp_PHFU=g@mail.gmail.com>
<[email protected]>
<CABUevEzYdfJ1pvreTM77xspNpnf5qko-_aMoLh+kC7Wdz6Gz6g@mail.gmail.com>
On 01/16/22 11:34, Magnus Hagander wrote:
>> https://www.postgresql.org/message-id/[email protected]
>>> *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
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: missing ML messages
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox