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 1miypb-0001jD-Ny for pgsql-www@arkaria.postgresql.org; Fri, 05 Nov 2021 13:00:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1miypZ-0000Bl-Dy for pgsql-www@arkaria.postgresql.org; Fri, 05 Nov 2021 13:00:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1miypZ-0000Bc-7t for pgsql-www@lists.postgresql.org; Fri, 05 Nov 2021 13:00:29 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1miypX-0008Au-29 for pgsql-www@lists.postgresql.org; Fri, 05 Nov 2021 13:00:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:References:In-Reply-To:Subject:Cc: To:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version:Sender: Reply-To:Content-ID:Content-Description; bh=nprOP9t0b61UEzauyxUqHgo8TOYg3ksv2s7X0kMYg1s=; b=Or7cmZC30NATZJtFnXBan7UKiv mWBVlNllcXQ5B/fhHQpucFsD+iXVX1kDYAM7PejSzNRaASgc/vu39hBDJKqa8LdaOVPfJ/7VtKFci gltvXxBCMxu2mBatrUMmCRyg318gj8/rQlI90NzSiQWqCY9EQXJ9W6JgINpdZE0fMts/NrrRCiK39 eIUdvVl6oHQ4YEtL61oC/qSg3eBC5CH10ogy7s6Nz9DdMbMP/Kbez0N8SIfs1lsRieKFxoYYP+GT0 R5wQlN3xdbnW3x8h/5zSXHtJcpshky7MUhYLtZsEiVoe3e4ztKYB89U7BoGC1FWr9CTHtxsuKSKVu eac4wTXQ==; Received: from meldrar.postgresql.org ([87.238.57.231] helo=webmail.postgresql.org) by meldrar.postgresql.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1miypR-0000SE-0j; Fri, 05 Nov 2021 13:00:24 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Sat, 06 Nov 2021 00:00:20 +1100 From: Justin Clift To: =?UTF-8?Q?C=C3=A9lestin_Matte?= Cc: Magnus Hagander , Alvaro Herrera , pgsql-www@lists.postgresql.org Subject: Re: [PATCH] pgarchives: parser: handle messages in which Message-ID is missing In-Reply-To: <72c93f94-1968-3939-2686-8e36e65b38fe@cmatte.me> References: <53316703-db69-7067-c82e-47a598711595@cmatte.me> <202111041947.x5su2sdjdx74@alvherre.pgsql> <72c93f94-1968-3939-2686-8e36e65b38fe@cmatte.me> Message-ID: X-Sender: justin@postgresql.org User-Agent: Roundcube Webmail/1.3.16 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-11-05 22:31, Célestin Matte wrote: >> Have you actually come across any case where a *proper* non-spam >> message is sent without a message-id and passes through actual >> mailservers on the way?  As a data point, I'm pretty sure it was the message-id field being missing from emails sent by scan.co.uk (a UK computer retailer) a while back, which caused their non-delivery to the mail servers here (@postgresql.org). So, being that we bounce them, it wouldn't at all surprise me that there's not much presence in our archives. :) + Justin