Jason
I am not its manager, just a user for more than 11 years.
This list obviously, and, I believe rightly, assumes that newcomers
write to ask one question and, to begin with, expect that one answer
will suffice. This implies that when writing the first time at least,
they are not (yet?) registered, and therefore would not get our replies
if they were automatically sent to the list only.
The way I handle what troubles you is by simply having defined an
account issuing a Reply-To: discuss@xxxxxxxxxxxxx, which I select (when
I do not forget ... ), to send my prose.
When my own address is added to that of the list, I get the same mail
twice, not always at the same time, which makes refreshing my knowledge
of the case a real hassle.
The case to which I added some info today contains 17 mails, to be
rememorized before answering seriously.
Jacques
On 01/24/2011 08:05 PM, Jason Stahls wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/24/11 12:44, Jacques Goldberg wrote:
Also please do not add CC to me, one copy sent to discuss@xxxxxxxxxxxxx
is sufficient.
There's something about the way the list is setup that makes the default
behavior for replying such that when you hit reply you only reply to the
person that posted to the list. This happens because the list sends the
from: header as the original writer, not the list. Is there any way to
change that? Thunderbird picks up that there's a list in the CC header
so it gives me another reply button for just replying to the list but I
can see how some are ending up with two copies of messages they're
participating in, one message Jacques posted had four different
recipients just a few hours ago.
- --
Jason Stahls
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNPb9YAAoJEBWmhVAMrS/gKNoH/1M58TgU482cOn3Bm6WMNs/O
M29ULQaPMqQhXwgn0DlIdQhT2adTUrZsw3IlfVMqYpMGrri7Ztuh3O0TGBxOfcpu
UfWjMYT6Lth/OeytioNdpOQgpPyYMqwC+SDJeLTxuquh1QjU8hUXcx+H1Z/es9Z2
F45PoCplKC2V6ItXQNR+nCDgobDzm5358T1gkpBArznltJYev8SMXpqB+b6LVQxA
ZTm0YbNPvCWJTJytTIXvHqf9aO2pvEnWOYa0bOfI4DX4gkGa4dZY7mVEVYRUlqNg
BrqOoyb1VdmxqfPc2CiR2u1sk2qrph2OZfUn81Sn1a+QA8tVHOGLqXlaamgeSf8=
=ihQL
-----END PGP SIGNATURE-----
