On Sun, Jan 24, 2021 at 02:37:33PM +0100, Magnus Hagander wrote:
> On Sat, Jan 23, 2021 at 4:14 AM Justin Pryzby <pryzby@telsasoft.com> wrote:
> > On Fri, Jan 22, 2021 at 10:07:38PM -0500, Tom Lane wrote:
> > > Justin Pryzby <pryzby@telsasoft.com> writes:
> > > > I noticed that one of my messages never made it to the HTTP page:
> > > > 20210119190720.GL8560@telsasoft.com
> > >
> > > I see it in the archives, and in my local mail folder too.
> > > https://www.postgresql.org/message-id/20210119190720.GL8560@telsasoft.com
> >
> > Ok...I must have entered it wrong somehow.
> >
> > So the problem is that it doesn't show up here:
> > https://www.postgresql.org/message-id/flat/20170907194236.4cefce96%40wp.localdomain
> >
> > Is it because I used two IDs in reply-to headers?
> >
> > In-Reply-To: <CAFiTN-updTo3aB+7vsECHOHpjB23Av5OfgZQrt90Q33gFK-oZQ@mail.gmail.com>
> > <CAFiTN-utJPbTLQ9i10wT_zmHX=un+RQMB1B1xbkTgrh971vqjw@mail.gmail.com>
> >
> > In mutt, I would've 't'agged two messages, and then ';'-'r' to reply and quote both.
>
> Yeah, I think that's it. We only parse a single value in the in-reply-to.
I wondered if you've tried to address this ?
+ Chapman Flack, who 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*
--
Justin
