Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113229 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 88891 invoked from network); 23 Feb 2021 15:58:20 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 23 Feb 2021 15:58:20 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0AEFD1804E4 for ; Tue, 23 Feb 2021 07:46:52 -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=-1.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,FREEMAIL_REPLY, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-yb1-f169.google.com (mail-yb1-f169.google.com [209.85.219.169]) (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 ; Tue, 23 Feb 2021 07:46:51 -0800 (PST) Received: by mail-yb1-f169.google.com with SMTP id p186so16946632ybg.2 for ; Tue, 23 Feb 2021 07:46:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=DhbOZdpNp2NNIOe9FS+FZMOvsJ7y7HbCvpo5jC716P4=; b=WV0rneqaXaaYdn0Jv190fyse9AmQ0vKKTUKjMi7kmIUrSVa21JfPocs8vmEjhBgakD vDjkp4+a/tfZ/0CKzZrLACnXZjND7znIWeD1CM/Cr8uh7OVEyJMtvMm2r1QTnJOw9PyL qWqYegtUSgkdv6JnJYiX4T3yXuBIkXGW//HF+XDLG/W3ipisPl+/ZrOanfQeBCYDYK+a NDDl8eRcVquHdFJudkSRKWcum1/OgZwI8DS67UbqBQAWekQnUgD+DYbc8Cd3MvdUlERf gwKgSqCBEhJ8RmVlBJD+b1Cj7F3tFoMY2PYwmEGDhAS1EY6MxZCpmz/Sr4SaTCDWDe1x 19xg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=DhbOZdpNp2NNIOe9FS+FZMOvsJ7y7HbCvpo5jC716P4=; b=ndoZSbQIDwygFp/jhfdVF81wUJtqqIZIbrhHXyiZnLLTiDsKT9YVGp2p0Kt4IiK8kw 0b5Qm5I2nH6fUWG+VdcRjgwo+L6xQ39VTGwQ92ICC93YaBLM84RCBLUQ3XDAofe17GfT u0tetNYnF+fpKRZyMd+Uqwy/3T1D4Vlhw1HPQ9Ng3xuhjt8+dvb6pG6e9DwdE0qRtjhO LpIC+yDdfNuGHb6bM5PHSePTQTLZU0KDMJhSQVrxwXDhWCT47Vn0B4NlFcFeyWq4K6iR wVydDjy5gtOWmqMga3+wTmO/mOyFnnMy0nLoryTFsNVPT37V0n7mA17owweYiJ1YbfgY 54aw== X-Gm-Message-State: AOAM532CD7S1sJCH7qPeNl4vAemUWWK/JgKBqNEpge2vbOahs0Mqi3u3 dL7H2bGqE+rEbSg1LCNlw/k4v78lqtV+60VzYByniSgD X-Google-Smtp-Source: ABdhPJxvILKwy0AhIeHrxxdPpu8lSHhhu4OnCCKspdwcVMfFmkwS/z+wqtY7k562cUaEWABm9846pb4lxd2BdwA0b9o= X-Received: by 2002:a25:e047:: with SMTP id x68mr39439204ybg.19.1614095203024; Tue, 23 Feb 2021 07:46:43 -0800 (PST) MIME-Version: 1.0 References: <1e4da591-0dab-420c-99a6-cf190c5cb98b@www.fastmail.com> <42866A13-C780-4783-A289-1564B725FE6D@benramsey.com> In-Reply-To: Date: Tue, 23 Feb 2021 07:46:27 -0800 Message-ID: To: php internals Content-Type: multipart/alternative; boundary="00000000000035c49605bc02d3b1" Subject: Re: [PHP-DEV] Replies on lists.php.net From: kris.craig@gmail.com (Kris Craig) --00000000000035c49605bc02d3b1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Feb 23, 2021 at 7:30 AM Chase Peeler wrote: > On Tue, Feb 23, 2021 at 10:27 AM Ben Ramsey wrote: > > > > On Feb 23, 2021, at 09:21, Larry Garfield > > wrote: > > > > > > On Mon, Feb 22, 2021, at 4:26 AM, Christian Schneider wrote: > > >> Am 15.02.2021 um 13:20 schrieb Pierre : > > >>> I noticed I receive almost all your replies to the list along with = a > > duplicated copy addressed to me or other conversation participants, I > think > > you always click "reply to all" instead of "reply to list" in your mail > > client. > > >> > > >> I think if our intention is that the default reply should go to the > > >> list then the mailing list should be configured to include a > > >> Reply-To: "php internals" > > >> header which it currently does not, right? > > >> > > >> This would make it harder to send a reply directly to the author (in > > >> some clients you have to click reply and then copy the address) but = it > > >> would not depend on the reply-to-list feature not all mail clients > have. > > >> > > >> - Chris > > > > > > +1 Endorse > > > > > > Also +1 > > > > I had no idea that it was double-sending messages to folks when I did > > reply-all. My mail client must filter the messages appropriately so tha= t > I > > only see one message, and I don=E2=80=99t have a reply-to-list option. > > > > Cheers, > > Ben > > > > > > > The gmail web client has the sender as the reply-to, and the list in the = cc > (at least in this case). On the receiving side, I don't get duplicates, s= o > I assume gmail is smart about filtering those out. > > -- > Chase Peeler > chasepeeler@gmail.com I also use Gmail and haven't encountered the duplicate message issue in quite a long time. +1 on the reply-to idea. That would represent a really easy fix, I think. --Kris --00000000000035c49605bc02d3b1--