From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KV9fK-00047c-Dg for qemu-devel@nongnu.org; Mon, 18 Aug 2008 14:41:18 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KV9fI-00045b-Fx for qemu-devel@nongnu.org; Mon, 18 Aug 2008 14:41:17 -0400 Received: from [199.232.76.173] (port=56421 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KV9fI-00045R-1a for qemu-devel@nongnu.org; Mon, 18 Aug 2008 14:41:16 -0400 Received: from fmmailgate01.web.de ([217.72.192.221]:60405) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KV9fH-0007s1-D8 for qemu-devel@nongnu.org; Mon, 18 Aug 2008 14:41:15 -0400 Received: from smtp08.web.de (fmsmtp08.dlan.cinetic.de [172.20.5.216]) by fmmailgate01.web.de (Postfix) with ESMTP id 72A6CEB5F49A for ; Mon, 18 Aug 2008 20:40:02 +0200 (CEST) Received: from [88.65.245.41] (helo=[192.168.1.198]) by smtp08.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1KV9e6-0000Jp-00 for qemu-devel@nongnu.org; Mon, 18 Aug 2008 20:40:02 +0200 Message-ID: <48A9C1FA.5060800@web.de> Date: Mon, 18 Aug 2008 20:39:54 +0200 From: Jan Kiszka MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig161DC49F0D8DCA6CEFCFFA1F" Sender: jan.kiszka@web.de Subject: [Qemu-devel] [RFC] remove enforced 'reply-to' for mailing list Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig161DC49F0D8DCA6CEFCFFA1F Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hi, some posters already ignore this hard-coded, rather untypical policy, other don't, and the result is sometimes fairly chaotic: Can we remove the 'reply-to' that is injected into every list posting? IMHO, it complicates things because carefully built up CC lists easily get lost this way unless you are replying to a mail you received directly. Mailman should have an option to avoid duplicate deliveries in case you are subscribed and on CC. Or is there any other reason for this 'reply-to'? Jan --------------enig161DC49F0D8DCA6CEFCFFA1F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkipwgAACgkQniDOoMHTA+kc1wCfcFnGX7P/CJxtvtm0Y6gG41XI nUsAnA1EVTXVwiyLEPhGv5XeBscLDVy8 =BWIe -----END PGP SIGNATURE----- --------------enig161DC49F0D8DCA6CEFCFFA1F--