[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: netiquette: CCing on lists



On Wed, Oct 29, 2003 at 10:12:49AM -0500, Bijan Soleymani wrote:
> On Tue, Oct 28, 2003 at 03:36:47PM -0700, Monique Y. Herman wrote:
> > > 
> > Upon reading this, I have to agree with you -- having a supposedly
> > private message sent to the list could range from mildly annoying to
> > outrageously embarrassing.
> > 
> > But then I have to ask -- do some clients automagically CC the poster,
> > or are people going to the trouble of CCing manually?
> 
> I hit the g key in mutt. It usually does do CCs. I'm told that there is
> a header that people can set to request no CCs. I think you mentionned
> something along those lines. I am pretty sure mutt respects that. I
> think most of the CCs you are receiving are from borken mail-clients
> that don't respect that header.

Shouldn't you be hitting the L key in mutt, for 'reply-to-list' instead
of g for 'reply-to-all'...
Especially considering that the code of conduct for the list:
  http://www.debian.org/MailingLists/#codeofconduct
says "When replying to messages on the mailing list, do not send a
carbon copy (CC) to the original poster unless they explicitly request
to be copied."

Contrary to what the opt-out spammers would have us believe, a failure
to request that you _not_ send me something doesn't constitute a request
_to_ send it.

I believe that when using the reply-to-list function, mutt will respect
a mail-followup-to header and CC the person if it's specified. At least
I know there's _some_ header that does the trick, because sometimes I
hit L in mutt and voila, there's a CC in my reply.

	Cheers!
-- 
,--------------------------------------------------------------------------------.
>   -ScruLoose-   | There are already a million monkeys on a million typewriters,<
>  Please do not  |            and Usenet is NOTHING like Shakespeare.           <
> reply off-list. |                        - Blair Houghton                      <
`--------------------------------------------------------------------------------'

Attachment: pgp4VSvSpjTjc.pgp
Description: PGP signature


Reply to: