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 1n98UM-0006rh-8g for pgsql-www@arkaria.postgresql.org; Sun, 16 Jan 2022 16:34:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n98UK-0001aX-KV for pgsql-www@arkaria.postgresql.org; Sun, 16 Jan 2022 16:34:40 +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 1n98UK-0001Y9-Ad for pgsql-www@lists.postgresql.org; Sun, 16 Jan 2022 16:34:40 +0000 Received: from mail-lf1-x12b.google.com ([2a00:1450:4864:20::12b]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n98UH-00068A-RE for pgsql-www@postgresql.org; Sun, 16 Jan 2022 16:34:39 +0000 Received: by mail-lf1-x12b.google.com with SMTP id e3so45844139lfc.9 for ; Sun, 16 Jan 2022 08:34:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kbe77My+dvsclGOT6rSfWEa23GNmeyMA01PWTYZRUYM=; b=NI+bzhCtiVmBCjkIPdLc4vtggOW9zTyBluuBrnq+7QERbWqlWyku785nyLJ+AqFV5S HGPu+ZYS3AOPlrCRpF+13kK13zKsas96wupqD/HnyT/KBpL7CWSPvUECgIByfCfslbX7 c4ky2tgYIlJJzFX26IeGqTFaJmf/mp3kGG/uTsOL7l4F5rBWa3lsG5pbHNFK0UZ8ANpM uwefJ9cPsx7yVW2Dg/17b3C/6aqjQ2zjODpVFTRe86nZ3fjRLXxUixMoGXNVphGisqPP 3Jhj8UOeAuj8G54ye5TewLIIx4Ih20pw4C+7gSLytcRy5JcNqHRchmzQy622I7xwXSVL eBOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kbe77My+dvsclGOT6rSfWEa23GNmeyMA01PWTYZRUYM=; b=uyOHsEl+NGQhSv5pTlXEPIhb/lnlQJTfb7TdvXkQraqZZDcwjEpC1vBz+a8DjruYrc pL1A0ZBGQqwOKGOH5ps6D5/uQn7u2ZDrTgI0nQ17YZn5LnjKMzoqj/c3zbDsTpGk59eV sEVQqp8nFpjyM06tJ/uI/ifh4qegRrc+ok91pPNWXr4lhQzWlqRsJDB5kw1uIfQMrG4c KljuRJYckTRcbu42sjQupoYerZTq8xw3erwpXdniZynl5nlwG19LyTqjY4XGpsFddGuT T0AJ2NtxwzAQk6M/iL9xMAvnt/46DqHt94abjuMrvg7FF3nLb7DtmyQ5F0o7gaD6ooXU v9lQ== X-Gm-Message-State: AOAM533XuqQEIofvERSg67cgMgizFdyPcUFj8Sv9maQ4QsgsokUKT1Cu Pf/v17EWZaHZzcNww1MkzpE7vJcqVyQTwQvJ7+Q3GMX9/5A= X-Google-Smtp-Source: ABdhPJyoQHE6r/DvSM5xC1i83oyiArlzU8leU7KfubFZpnbb7GlDhZXVyhoJGeKOQe0Saocec/syGgeJ8AfPYMyKW5Y= X-Received: by 2002:a05:6512:3191:: with SMTP id i17mr14092769lfe.496.1642350875499; Sun, 16 Jan 2022 08:34:35 -0800 (PST) MIME-Version: 1.0 References: <20210123025941.GA30285@telsasoft.com> <1287447.1611371258@sss.pgh.pa.us> <20210123031431.GI27167@telsasoft.com> <20220109193535.GM14051@telsasoft.com> In-Reply-To: <20220109193535.GM14051@telsasoft.com> From: Magnus Hagander Date: Sun, 16 Jan 2022 17:34:24 +0100 Message-ID: Subject: Re: missing ML messages To: Justin Pryzby Cc: pgsql-www@postgresql.org, Chapman Flack Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, Jan 9, 2022 at 8:35 PM Justin Pryzby wrote: > > On Sun, Jan 24, 2021 at 02:37:33PM +0100, Magnus Hagander wrote: > > On Sat, Jan 23, 2021 at 4:14 AM Justin Pryzby wrote: > > > On Fri, Jan 22, 2021 at 10:07:38PM -0500, Tom Lane wrote: > > > > Justin Pryzby 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: > > > > > > > > > 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 ? I have not personally had time to look into it, no (I assume you meant this for me, even though you addressed it primarily to Champan, who previously did not participate in the thread). And apparently neither has anybody else. > + 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* It should be noted that pglister does exactly nothing with it and should pass it through without making any changes whatsoever. The question is what happens when it hits the archives, which are not part of pglister. Which of course still needs to be handled. 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? -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/