Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113206 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 7485 invoked from network); 18 Feb 2021 13:50:46 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 18 Feb 2021 13:50:46 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id A851B1804B1 for ; Thu, 18 Feb 2021 05:38:00 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=BAYES_40,SPF_HELO_PASS, SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail.toneristzuen.de (mail.toneristzuen.de [84.19.169.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 18 Feb 2021 05:37:59 -0800 (PST) Received: from maniacmansion.fritz.box (ppp-188-174-60-93.dynamic.mnet-online.de [188.174.60.93]) by mail.toneristzuen.de (Postfix) with ESMTPSA id C8355412C9 for ; Thu, 18 Feb 2021 14:37:57 +0100 (CET) Message-ID: To: php internals Date: Thu, 18 Feb 2021 14:37:53 +0100 In-Reply-To: <4972baf7-606d-4bff-bacd-223d816e0ec7@www.fastmail.com> References: <4972baf7-606d-4bff-bacd-223d816e0ec7@www.fastmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Replies on lists.php.net From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Mon, 2021-02-15 at 16:43 -0600, Larry Garfield wrote: > This is a long standing fight. Who is in the wrong, mail clients > that stupidly send double messages, or mail clients that stupidly > can't detect and omit double messages? Probably both, but the one > that is really wrong is whatever someone else is using and you're > not. Because humans. > > (Personally I'd blame the ones that lack reply-to-list, because > that's the easier feature to include.) > > Could we at least update that page to say "use the reply-to-list > feature if available, or reply-all if not"? Or something like > that? Because yeah, I'm also really sick of getting 2 copies of > every email sent to every thread I ever touch. :-) > I use the reply-to-all feature purposely (well, now I didn't :-D) * I don't know if the sender is subscribed (with well-known names not a problem, but not every sending a mail is necessarily subscribed) * I don't know if everybody on the CC line i subscribed (be it an individual or another list) * As a recipient I have a different attention to a mail in the mailing list folder (sorted by list-id headers) and the onein my inbox This affects both responses and somebody CC'ing me johannes