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 1miii2-0007IY-WE for pgsql-www@arkaria.postgresql.org; Thu, 04 Nov 2021 19:47:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1miii1-00089T-VX for pgsql-www@arkaria.postgresql.org; Thu, 04 Nov 2021 19:47: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 1miii0-000885-Pn for pgsql-www@lists.postgresql.org; Thu, 04 Nov 2021 19:47:37 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1miihx-00078u-FW for pgsql-www@lists.postgresql.org; Thu, 04 Nov 2021 19:47:35 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id AB0515C0072; Thu, 4 Nov 2021 15:47:32 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 04 Nov 2021 15:47:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=xJxC0vViVozdUkSohFe6+N+qZYVdeJwaahrRWlaS/mk=; b=JEHnFU4p 02L5Gr1V8d0HNrHue1SOt9h4sMyR7PdlDLbj/Yq81XR3wxKcl/FAZVaHkIKRxr/x I8q3XvNJqJ/aaeZzJI2sto2G8Z4EHWkS/7qrU8tvXRWDpBPPjgI4EtRosPmAIMeJ XqgNlSzYf7UDgle8JvQR/PGPV1Xzx55baktOAHSR2IQ66/2cUWGpOzoTzLHNbpip BbDi8JXzLyMQy+fgk2qeBs5MTmVtG+1U1HfTdDuYywXsJihj5vhdY63zQSTrANnt wmtrTf7nr+avXAuthKzcb+9Dql6gpcdikU6oyHsTEK3qIBMvdA0Ez5DSAVzZvL7/ 5nSzsSaODanhVQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrtdeggdduvdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpedujeevjeffjeevuddutedvkeeiueeitddvieelfeekveej udefgeeuvdejhfeuleenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhh vghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 4 Nov 2021 15:47:31 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 075082A0804; Thu, 4 Nov 2021 16:47:28 -0300 (-03) Date: Thu, 4 Nov 2021 16:47:28 -0300 From: Alvaro Herrera To: =?utf-8?B?Q8OpbGVzdGlu?= Matte Cc: Magnus Hagander , pgsql-www@lists.postgresql.org Subject: Re: [PATCH] pgarchives: parser: handle messages in which Message-ID is missing Message-ID: <202111041947.x5su2sdjdx74@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <53316703-db69-7067-c82e-47a598711595@cmatte.me> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-Nov-04, Célestin Matte wrote: > > I don't think this should be the responsibility of pglister. As you > > say, "most MTAs do add this field" -- and the solution is to > > configure the MTA to do this. We already rely on the MTA to get a > > lot of other important things right. > > But then these messages will get delivered by pglister but pgarchives > will fail to archive them, although they do not actually break > requirements. Shouldn't we follow the RFC here? Maybe pglister should refuse to deliver messages that don't contain a Message-Id. -- Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/ "Ninguna manada de bestias tiene una voz tan horrible como la humana" (Orual)