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 1mixRU-000624-6X for pgsql-www@arkaria.postgresql.org; Fri, 05 Nov 2021 11:31: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 1mixRT-0005bj-5I for pgsql-www@arkaria.postgresql.org; Fri, 05 Nov 2021 11:31:31 +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 1mixRS-0005ba-Sd for pgsql-www@lists.postgresql.org; Fri, 05 Nov 2021 11:31:30 +0000 Received: from ploudseeker.com ([78.199.165.48]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mixRP-00061a-Rg for pgsql-www@lists.postgresql.org; Fri, 05 Nov 2021 11:31:29 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cmatte.me; s=myselector; t=1636111884; bh=2oelHDauvxQxcnxZTCJp6mlwHbP+ieeKewQi6jy3lWQ=; h=Date:To:Cc:References:From:Subject:In-Reply-To; b=PVsfZqzjiEjiafoDqihre7SD4UDQKF1ibfrDibT5n9FbV0XBY7Et6F2yCOjGbXke8 RS3FVGqfpGeKCgiqx5oXK8BvsA3PvGvQ6lvmQy4Gzejo0xV4QCouRZzV4OA9t+nUHf sxJx5v5MSS7lEQM+KIJZBJZfc3WWv9YYbjlAFd3OV15IOE7DKM3wke+yAFYsOzuUr0 O1aaFdQu51W35x9bwSi6txDxYF3ytvipL9hlqOid1lvDnVfxixS+1pNov6hz8j4F7Q 34UI8zytKrPxXPjEewpzM0A0WhBpbc4luc08v/M1LWykHu6kNYJlnEwzhAXP4JCoPd Lrpkjc5NZTwjg== Message-ID: <72c93f94-1968-3939-2686-8e36e65b38fe@cmatte.me> Date: Fri, 5 Nov 2021 12:31:23 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Content-Language: en-US To: Magnus Hagander , Alvaro Herrera Cc: pgsql-www@lists.postgresql.org References: <53316703-db69-7067-c82e-47a598711595@cmatte.me> <202111041947.x5su2sdjdx74@alvherre.pgsql> From: =?UTF-8?Q?C=c3=a9lestin_Matte?= Subject: Re: [PATCH] pgarchives: parser: handle messages in which Message-ID is missing In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > 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?  > > Looking through the approximately 1.4 million mails in the postgres list archives, not a single one has a message-id generated by the archives server MTA (which is configured to generate it). Not a single one by our inbound relay servers. And exactly one by the pglister server -- which turns out to be a bounce that ended up in the archives because of a misconfiguration back in 2018 that's not visible in the public archives. After some tests, I do have a very few number of non-spam examples (3 emails from 2 different people in a postfix+mailman mbox of 5k emails), but they date from 2003-2007. Exim already handles empty Message-IDs by default by generating them [1], although it will let a message with Resent-Message-ID pass through as-if. I tested such a case, and pglister seems to actually drop the message (or fail silently). [1]: https://www.exim.org/exim-html-current/doc/html/spec_html/ch-message_processing.html#SECID226 -- Célestin Matte