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 1tnXKX-0067hy-Ld for pgsql-bugs@arkaria.postgresql.org; Thu, 27 Feb 2025 06:25:10 +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 1tnXKW-006iuk-BT for pgsql-bugs@arkaria.postgresql.org; Thu, 27 Feb 2025 06:25:08 +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 1tnXKV-006iub-U6 for pgsql-bugs@lists.postgresql.org; Thu, 27 Feb 2025 06:25:08 +0000 Received: from mail-pl1-x630.google.com ([2607:f8b0:4864:20::630]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tnXKS-000KK4-1O for pgsql-bugs@lists.postgresql.org; Thu, 27 Feb 2025 06:25:06 +0000 Received: by mail-pl1-x630.google.com with SMTP id d9443c01a7336-220d132f16dso7101475ad.0 for ; Wed, 26 Feb 2025 22:25:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ardentperf-com.20230601.gappssmtp.com; s=20230601; t=1740637504; x=1741242304; darn=lists.postgresql.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=bidYeRQjqv7K52Oe1GGXwXc429XOgQOOYK8kORrn0+0=; b=wanJ0wrlcSXsidsQ/5TwZk42Iq3xGTDwNKz11R+u3qW0vmOTmdPFjY96sVzw+5vFmV 9rSM4iSMJuIFepI7jxeUp1lJUXc1BayHMSag4CSMgOHl2CA9DCUL9oeZO6Bu7pgdk2eJ Opy188XXoQclYfUwDkoHrjE3ptS37/f2TT8dHdgiIUjxDLmS4g1GEsA2jUeBgNT1/Eq7 0MSw4RxI3UFuoY2+/lYI3LwLs/u7WoPRrfbqTijoib9BPb5Yp7Z3j4c1sOL74qCHhqOV EzReRNDLxpHu0ICgIe2ysa/sI/VjBiG/jfN5DZC8h2iquJ4Y0eGH1Tux0boZ+8zEztlp 1dqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740637504; x=1741242304; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=bidYeRQjqv7K52Oe1GGXwXc429XOgQOOYK8kORrn0+0=; b=Fo4ik/XTtfJ8D24ZYi4lPuNCbapRhSujseYqffx3hDUysDn8DqhhWw2qc5rFAws/ao M56u8g4Xugbz+AKGqhXZFmBMKZkK8TTZvarvNqyVb/Bvu2KwV/hHMLWnGEU/L2E9WJ2Y UYbtT4rxzRu5DXiAch3Lhhg/jJokiyZEKpxVKzN6qsQDBMpb7COz+UVv8NbytYY4sh8G 8bH+6I6tot+QjoKYQE0YtreuIudgYSbNd41WoMvwsYzW3YQak+H7YoElJFUKyOXMPkQB ZAIv0YgvM2ZOw8fzuyS65ObP5KmzI9I+7Wa/GlZb6v0yrYGwSKbbwe3NDLFDqWw8BXjD fc7A== X-Forwarded-Encrypted: i=1; AJvYcCXGsiMdVoU5/ZZQJhSi1ruWzgBRijwFI307eJx1z6A+ta9++nnyXSFEkmzgC8Q/34HTodfZMNQ//zK0@lists.postgresql.org X-Gm-Message-State: AOJu0YxKekLy3u/lv9NwRDXGac1XhqtxdhKIKx8wEBfKVKyplXKKb62P Jos4zVPduw4Zkmgkvg+Veiu6y/K8e5rn2mJWj2XRMZXKYELpXkg59F1jwoorfQ== X-Gm-Gg: ASbGncueo/d70sTpgUbWDSudFFmqgz0HlL5THV+GLl2pxeEw5YkGkkZ+49KRD38Ei7/ 9VLx51573I2Gm4xjYlPJvmpwWSs02HaiYP6hSiCfllRzxAbDVWA0q6G2oWr98H5aX4/hPo1PmyT NmkDW1ZUvuUiyilm3OkMZf0nozE+uUpCNSvsbAavnT69u1kBFoPZ3ziruyIA3faHnUmRuVmV63k RAdkrksSELMKmf03OwCf92Eow6czNJzzALDFx7ftcAXnSFdYfSU1b07ilvbGQqjJ9icXldxX77O 1oKuZa23ctSfApsroffPcMEoXaHwyAAugMmsF2f6xjP+7KE0IzyIl6HXDFFVFGnv X-Google-Smtp-Source: AGHT+IG/nU3q0QVAJuLLJ0mA5LSd3M4wvXZ7pzDjA6Nxrp1KiudFLDsUVbIMO+GL41+CymVKwCF9wg== X-Received: by 2002:a05:6a00:2d8e:b0:730:9567:c3d4 with SMTP id d2e1a72fcca58-7348bd9131cmr10796177b3a.3.1740637504356; Wed, 26 Feb 2025 22:25:04 -0800 (PST) Received: from ardentperf.com (97-113-79-118.tukw.qwest.net. [97.113.79.118]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-7349fe2b7d5sm716395b3a.6.2025.02.26.22.25.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 26 Feb 2025 22:25:03 -0800 (PST) Date: Wed, 26 Feb 2025 22:25:02 -0800 From: Jeremy Schneider To: Bruce Momjian Cc: Greg Sabino Mullane , 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: <20250226222502.4e56d6e2@ardentperf.com> In-Reply-To: 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-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 24 Feb 2025 10:55:31 -0500 Bruce Momjian wrote: > On Mon, Feb 24, 2025 at 10:47:26AM -0500, Greg Sabino Mullane wrote: > > On Mon, Feb 24, 2025 at 4:45=E2=80=AFAM Matthias Apitz > > wrote: > >=20 > > Why postgresql.org can not do the same? > >=20 > >=20 > > 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. =20 >=20 > 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. Well to be clear, I think lots of us don't love DKIM. If I recall correctly, Amazon turned it on somewhat recently and broke all their employees ability to use company email with the any major mailing lists. Not just postgresql but also LKML, IETF, etc. And Amazon is not the first. There is documentation on the internet of Intel [1] and=20 Google [2] doing the same. And don't use Yahoo for your personal email, who famously back in 2014 broke every mailing list in the world [3]. Back when I worked at Amazon and they started enforcing, I didn't bother complaining - I just permanently switched to using my personal gmail account for open source mailing list participation. I think the whole DKIM thing is a mess but I don't think it's a postgres problem. -Jeremy 1: https://lore.kernel.org/lkml/20211214150032.nioelgvmase7yyus@meerkat.local/ 2: https://news.ycombinator.com/item?id=3D13425802 3: https://mailarchive.ietf.org/arch/msg/ietf/J-IsfA0Lb-6T_NeMD1ENKZyb9tA/