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 1n6dyr-0002Ur-Il for pgsql-www@arkaria.postgresql.org; Sun, 09 Jan 2022 19:35:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n6dyp-0001ba-FG for pgsql-www@arkaria.postgresql.org; Sun, 09 Jan 2022 19:35:51 +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 1n6dyp-0001bQ-35 for pgsql-www@lists.postgresql.org; Sun, 09 Jan 2022 19:35:51 +0000 Received: from mail-io1-xd2d.google.com ([2607:f8b0:4864:20::d2d]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n6dyb-00052H-Qx for pgsql-www@postgresql.org; Sun, 09 Jan 2022 19:35:49 +0000 Received: by mail-io1-xd2d.google.com with SMTP id 19so14798542ioz.4 for ; Sun, 09 Jan 2022 11:35:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Hm1l5ZcOxWHCTirDKJMurquiX/a+AwWdpe+4AhA1VeI=; b=glVQgb2HXeW02IXGfyUn158jrG4T4Xaa+aXO9a23wNhMyBv9JgiBA1PHFgoLhpu1zM q6u5sBfdym45h/cLZMpiuSvCJwIgMjCFP4rWEDsN6eod6J6C7CEhojZbSNKs/zRm4xIi X11j4QambB3MR4xd2XNJ+qj8KHh4YukO4vhltaScpKM78BDEn0g85pl8eTGufzkzx5wT awZCV6cDnIMXn4TkQYQnslDmYeZ9N6Mmt9TRnIZsczqPkmALc1ff9Gb9RnGsIKxrjVVW sbJzLBKQPOCq+6nYxHymV37sG5A1/eQJfJRF76ZNvLEByJVRO72n89ayCVaCJqhaENV+ fqVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Hm1l5ZcOxWHCTirDKJMurquiX/a+AwWdpe+4AhA1VeI=; b=bGt+vbtPv83jZqW2oecN88iG0qdS5KfQUSmF4I0HFKFOxwVWdJVEC29uJGkhntKyEY 21poYZS+QlvAXDBZsLDC13aCWZHFBWsigQEd5bSbstDCUjnKBMJ610IUWY6i1gXDtwM3 1CqDi/jJOdXzwhLwnACYz7wxIa3N9giy8GwaY0+9caAWRcmoDDzdNYmiZoDoZ10taSb0 XHBPlaPVquWxNOoLsPirrpTlH8SpCGhc0KTbBCdwZGyXy127+uEbvb82hEL1XmLsTm+p re5IkWWPc+m/AylD6Z71OZXl4KTGDOY6MHxFLtFfLWNTP963DqLCn648xlE/vrO+WMKD QOXw== X-Gm-Message-State: AOAM530mz8mSZtr3/i/2iz6S1uqoD+U30AgbaPpmNxodjQDW/Ig2HvEc pVzhvnc01pZ0zT3Bzp/UWP1cZbw0OyBBkQ== X-Google-Smtp-Source: ABdhPJymMje0WtstTwdZs4o36tCEux/5fVfN8UT0UuZLITTDzeMW7KfNyoAcbg0VC+tRrIxrQJuxNA== X-Received: by 2002:a02:9445:: with SMTP id a63mr650312jai.102.1641756936886; Sun, 09 Jan 2022 11:35:36 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id j8sm2867944ilk.13.2022.01.09.11.35.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Jan 2022 11:35:36 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 6AFAB800A78; Sun, 9 Jan 2022 13:35:35 -0600 (CST) Date: Sun, 9 Jan 2022 13:35:35 -0600 From: Justin Pryzby To: Magnus Hagander Cc: pgsql-www@postgresql.org, Chapman Flack Subject: Re: missing ML messages Message-ID: <20220109193535.GM14051@telsasoft.com> References: <20210123025941.GA30285@telsasoft.com> <1287447.1611371258@sss.pgh.pa.us> <20210123031431.GI27167@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 ? + 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