Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tmany-007uOs-6v for pgsql-bugs@arkaria.postgresql.org; Mon, 24 Feb 2025 15:55:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tmanx-004Ipt-DI for pgsql-bugs@arkaria.postgresql.org; Mon, 24 Feb 2025 15:55:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tmanx-004Ipl-3z for pgsql-bugs@lists.postgresql.org; Mon, 24 Feb 2025 15:55:37 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tmant-000V5W-3A for pgsql-bugs@lists.postgresql.org; Mon, 24 Feb 2025 15:55:36 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=owTRFWgp+v2hIoKANsc7pC1ISvflgVPBm7BdHR/RX6M=; b=r/aC5yiQhhISmqygODndHFnXvC s9DomJ4ak0otWgaUu9HtyeOj68RLRj8rZtextHq8vO7uCLqzoJ+RvpYD2QBrIiqosy8jvdlO+ZqyF kWbqVLxbI95BJTba8YjWEbXyB8TLGObCETD2bbNF6hyxq9zd+L6Fiu47kDybvXOXGCLOdPVU17hwK b+WHq3Ke13AzSYLvO+/SwsTtCN58GS9XBOPDbjdqDiM6YXqrwLZU8oPZcg5/MSH+kJPRGTyf7PVCq iUlG9Nc6PPCECfe/jyuYwzZ+LCKqHeV5yhS1A62+H6/TYTojrXnoI0nIJbQjS9kWmhPbHfS//JiPX Bs5VSXBw==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1tmanr-005E8S-0I; Mon, 24 Feb 2025 10:55:31 -0500 Date: Mon, 24 Feb 2025 10:55:31 -0500 From: Bruce Momjian To: Greg Sabino Mullane Cc: Matthias Apitz , Stefan Kaltenbrunner , Tom Lane , pgsql-bugs@lists.postgresql.org, Magnus Hagander Subject: Re: BUG #18822: mailing lists reject mails due to DKIM-signature Message-ID: References: <18822-25d115fe42e642c2@postgresql.org> <7d1cf55f-4228-49d8-8066-cf96deab8ad3@kaltenbrunner.cc> <82011.1740245157@sss.pgh.pa.us> <48eac131-cf99-4753-8b11-dfdc2965ac00@kaltenbrunner.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Feb 24, 2025 at 10:47:26AM -0500, Greg Sabino Mullane wrote: > On Mon, Feb 24, 2025 at 4:45 AM Matthias Apitz > wrote: > > Why postgresql.org can not do the same? > > > Honestly, it's worth pointing out that you are the only one complaining about > this issue. Were it hundreds of others, we might react differently. But since > it's only you, it further supports the "your problem, not ours" prognosis. He did point out that many other mailing lists are fine with his configuration, so that works in his favor. I think we are just more precise than those other lists. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.