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 1t0pxg-00DRNL-VX for pgsql-general@arkaria.postgresql.org; Tue, 15 Oct 2024 22:24:16 +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 1t0pxd-00CHnJ-Ej for pgsql-general@arkaria.postgresql.org; Tue, 15 Oct 2024 22:24:13 +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 1t0pxd-00CHnA-2z for pgsql-general@lists.postgresql.org; Tue, 15 Oct 2024 22:24:13 +0000 Received: from mail.hjp.at ([212.17.106.138] helo=rorschach.hjp.at) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t0pxV-0014ae-Ie for pgsql-general@lists.postgresql.org; Tue, 15 Oct 2024 22:24:12 +0000 Received: by rorschach.hjp.at (Postfix, from userid 1000) id B11EF224B0; Wed, 16 Oct 2024 00:24:01 +0200 (CEST) Date: Wed, 16 Oct 2024 00:24:01 +0200 From: "Peter J. Holzer" To: pgsql-general@lists.postgresql.org Subject: Re: Questions about document "Concurrenry control" section Message-ID: <20241015222401.qtxdjrwtbvmh4aht@hjp.at> Mail-Followup-To: pgsql-general@lists.postgresql.org References: <2852693.1728656353@sss.pgh.pa.us> <32ae50a3-b6a3-4ca2-8051-9b0261ac430b@iseki.space> <2fb0b1df-c06c-4a0a-af2a-ea57ecb6ed79@iseki.space> <0509ee4e-75dd-409b-b30b-b136805fbd15@aklaver.com> <20241012101719.k5iyqptjo6sx2sro@hjp.at> <31b8f5be-ba8d-4252-bcd6-4cd6f2742df9@aklaver.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="kojwd36aw6n5yvwd" Content-Disposition: inline In-Reply-To: <31b8f5be-ba8d-4252-bcd6-4cd6f2742df9@aklaver.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --kojwd36aw6n5yvwd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2024-10-12 09:02:37 -0700, Adrian Klaver wrote: > On 10/12/24 03:17, Peter J. Holzer wrote: > > On 2024-10-11 21:21:16 -0700, Adrian Klaver wrote: > > > On 10/11/24 20:10, admin@iseki.space wrote: > > > > I found. Maybe we should reply to the mailing list only. Otherwise = we'll > > > > receive multiple copies of the emails. > > > >=20 > > > >=20 > > >=20 > > > Not if you go here: > > >=20 > > > https://lists.postgresql.org/manage/ > > >=20 > > > and check: > > >=20 > > > Don't receive an extra copy of mails when listed in To or CC fields > >=20 > > Yes, but that's the wrong way around. Then I get some mails only > > directly and some only through the list, which makes proper filtering > > hard to impossible. For me it's much better to get all the mails through > > the list (so I can use the List-ID header to filter them into the > > appropriate folder) and live with the extra copies in my inbox. I would > > prefer to not get those extra copies, but there is nothing the list can > > do about them, that's under the control of the sender. >=20 > Not following. If it goes through the list either by 'Reply to list' or > Reply All' it is going to pick up the List-ID and be filtered. All the > setting does is make sure you don't get extra copies when your email is in > the To or CC fields, which is the list doing something about them. What it is doing about them is to drop the message (it can't do anything else). So if I send a message to adrian.klaver@aklaver.com, pgsql-general@lists.postgresql.org you will get the copy sent directly to your address (which won't have any List headers set), but not the copy sent to pgsql-general@lists.postgresql.org. So basically you don't have any reliable way to detect that the message was sent to the mailing-list (the best bet is probably to filter on the To: and Cc: headers, but that may fail (both with false positives and false negatives); some mailing-lists put a tag in the subject, but nobody removes that for a private reply. > I've been using this for years and aside from some general list/email > issues it has worked as advertised. Maybe you like the way it works. I find it useless, because it does exactly the opposite of what I would want it to do (but I know that that's impossible). hp --=20 _ | Peter J. Holzer | Story must make more sense than reality. |_|_) | | | | | hjp@hjp.at | -- Charles Stross, "Creative writing __/ | http://www.hjp.at/ | challenge!" --kojwd36aw6n5yvwd Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEETtJbRjyPwVTYGJ5k8g5IURL+KF0FAmcO63sACgkQ8g5IURL+ KF3dLQ/9FCCj2UKTLG3/sAL/Ycb/efEMB11Mpzu0SV+tH4Gbb4DHnVud+YX+TiVY Og9CPpws8ryuzaHgEsbLIUVaxzZXPekz5IqqSlcdSs5IIeUNGsFvM0NaCRc929fX nQRgcK4KbxR4X8S7htI6M6/QoqMJn6NhiBun+gOqof7V+NGelw2eB3f2X7Tx5St5 SghDB6H4tZG9pp8qMnbP5zurR1hTuaue4Y0+2C2GRLLMyHAumw3EkmIaeKY/cwu0 5smR5ox4K5cxyXGI7JHUrcLhP8OXWb5CWbj3oCphrqyUMnH5Mv+MsgAb2RZqS0EE 8OgTTZbRNnSpjeJFnCLj6qvA5DzkoggreQCrJzEWHAZk8j8lnrHOXtt2wEeMt8xt NTrIrVxur3woIYHT+dy+X7a7E9LrPWI7Wz3S7WihqQc60+JidPgvDXxAkiLUxFtm t1BHT0JW3MTSgmt/Vg4xI5HUdU6f8CsByaVcFyme5i5eSL6WRrm8+pvVvlXwOkQO SFJ2R7jU0EC7fZu7u78VoyDLuWiRuk0z1ZRxpkDtBFCgtqIEUD6mPBDwoSFLaMPJ D1FYIYzVe6duzjHj2h2uTCzwJHB32Jtq9Z7cJzrvzx1Y8ADaydja4F7avTi9pRHa SmM7US3jz5K88Z+Xxt8VnZ0unuR+8PozTHCiA0bwSO9L8GQK+iU= =3e70 -----END PGP SIGNATURE----- --kojwd36aw6n5yvwd--