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

Re: Cc: to poster (was Re: OT: less v. more...)

On Thu, Aug 03, 2000 at 10:34:35AM -0500, Bolan Meek wrote:
> Gerfried Fuchs wrote:
> > 
> > On 02 Aug 2000, Bolan Meek <Bolan.Meek@wcom.com> wrote:
> > > On topics arisen from this discussion,
> > > Gerfried Fuchs wrote:
> > > > ...BTW, please refrain from sending to _both_ the list and me,
> > > > I read the list. ...
> > > One may assume that those whose names one sees often
> > > are subuscribed, but how to be sure, generally?  I propose
> >  ...In general, on open lists you should assume
> > one is reading the list s/he is posting to....
> Ah, good, so, with this assumption, one ought to remove the
> personal To:'s and Cc:'s, unless requested? (Like you did..)


Posts to list are responded to on list.  Mutt supports this through the
"L" (rely to list) keybinding.  This also gets around (and moots) mailing
list software that defaults to "reply to sender" rather than "reply to
list".  My procmail filters tend to dump list mail cc's to my list folder
-- cc's to me just result in duplicate items within the list folder.

I'll cc a person who requests an off-list response.  I generally don't
cotton personal requests I recieve as followups to a response I've made
on list (with or without a cc), though a status update is sometimes

I'll forward a direct support request made to me rather than a list to
the list unless it comes from a personal friend.  I find this behavior
unspeakably rude.  I've had this policy for years on a number of mailing

...and I generally try to scan headers to see that I don't propogate cc:
lists, though I'll sometimes slip.

Karsten M. Self <kmself@ix.netcom.com>     http://www.netcom.com/~kmself
 Evangelist, Opensales, Inc.                    http://www.opensales.org
  What part of "Gestalt" don't you understand?   Debian GNU/Linux rocks!
   http://gestalt-system.sourceforge.net/    K5: http://www.kuro5hin.org
GPG fingerprint: F932 8B25 5FDD 2528 D595 DC61 3847 889F 55F2 B9B0

Attachment: pgp0_ei2tBnOw.pgp
Description: PGP signature

Reply to: