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 1l39Nm-000812-BY for pgsql-www@arkaria.postgresql.org; Sat, 23 Jan 2021 03:14:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l39Nl-0001q4-7w for pgsql-www@arkaria.postgresql.org; Sat, 23 Jan 2021 03:14:37 +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 1l39Nl-0001px-36 for pgsql-www@lists.postgresql.org; Sat, 23 Jan 2021 03:14:37 +0000 Received: from mail-io1-xd33.google.com ([2607:f8b0:4864:20::d33]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1l39Ni-0000sR-KA for pgsql-www@postgresql.org; Sat, 23 Jan 2021 03:14:35 +0000 Received: by mail-io1-xd33.google.com with SMTP id z22so15352924ioh.9 for ; Fri, 22 Jan 2021 19:14:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=evqLeFCwQhhndX4R8HrczXtddVYTy3V6uDKmt6MOdMo=; b=twJr2kkfNnBW9SLRtZ2NZWE1TWyys3wERRV7lpnDAErSyXmZE8lA+pnkAn8noHbWeK EsuF1THwOGEqm1PtXZuugaSlGRgp/T1CSXHzWCmDa8r2k9B7b1thNwiNjZb/jjXy56dN lRkAIRQIoUo3UrMjXi3OKCv4z613S49CRrC5JNRwr2Koj/1JNie0c+35JwiP0HsHSbOo WtnqbmrcizomVj7ExleAypjtxVhgn2qvkPwRWzmD+diYw7MqELpD1+Pw5uNGEFTOtELQ tHxB5GrRwX+w3OSr1aYFZwOZ/tZ35Hyd00jYYbfuVoSF1HfpnehXt2yKY3+didKqcLqs TMtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=evqLeFCwQhhndX4R8HrczXtddVYTy3V6uDKmt6MOdMo=; b=aGP8O3mBgDqNOnckSVdZNgw2XDCB7OhDWcwBCJfb8Zopa0uTlecmLhNu/4t2JDV2G/ QUT6hv3A3amOOofqmTEH9RhlfcqnkNIk3WjYWUVX2PsG0LJvqQYOX8C+/2xl11IGsUwc rwO1FFJ40u6d5Nja7+/hV2z1s7eJ5JxAyL/bqWT72iMPbjZxhAggzj3PP1kpdg0A7spc aICe01bfSgXEQASLBV1SlnlRbo/HTR4RUl0MzI+qHrs4UrItSaU6Ka4hybW0dX68P+LI n+qZoGvgkfL9ezyadE/1v05QPtFoZZfT3OjIbTTUs+rZ3WatdXGCDZ8UG81Cw5EsCbxH CKUw== X-Gm-Message-State: AOAM531MXXC8jsoZdHkTwqQSJR0c5zUYw0C/ln2m6zkRxMKMaJcm36h1 cA1AJlAs+TGcmCyYcrMDHC+/ErK63nnOtQ== X-Google-Smtp-Source: ABdhPJx42X4gi4Z9MPGpQtF+Bj0mtpXqdA7iYbJsIai3oqT4IWZWRXTOBV6EfnYoI/LqSjZ/0S7u0w== X-Received: by 2002:a5e:de41:: with SMTP id e1mr753254ioq.135.1611371673379; Fri, 22 Jan 2021 19:14:33 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id d5sm7460289ilf.33.2021.01.22.19.14.32 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Jan 2021 19:14:32 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 8243280076C; Fri, 22 Jan 2021 21:14:31 -0600 (CST) Date: Fri, 22 Jan 2021 21:14:31 -0600 From: Justin Pryzby To: Tom Lane Cc: pgsql-www@postgresql.org Subject: Re: missing ML messages Message-ID: <20210123031431.GI27167@telsasoft.com> References: <20210123025941.GA30285@telsasoft.com> <1287447.1611371258@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1287447.1611371258@sss.pgh.pa.us> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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. -- Justin