Great Circle Associates List-Managers
(February 2003)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: PLEASE DO NOT CC ME ON MESSAGES TO THIS LIST
From: "David W. Tamkin" <dattier @ panix . com>
Date: Tue, 25 Feb 2003 10:25:20 -0600
To: <list-managers @ greatcircle . com>
References: <5.1.0.14.2.20030225052754.4b2fe140@199.74.151.1> <15963.28944.963000.741431@gargle.gargle.HOWL> <82952656.1046166301@[192.168.254.79]>

Tom Neff wrote,

| This is kind of a band-aid, though, and a risky one.  For one thing, just
| because a list server THINKS it sees a member address mentioned in a
| recipient header, doesn't actually mean that the message got there.  The
| address in question might be set up to only allow mail from the list server,
| in fact that's a common spam protection technique.  In that case the Cc'd
| member would get no copy at all.

Not only might the delivery of the direct copy fail, but it might not even be
attempted.  In a previous incarnation of this discussion, someone pointed out
that a list member's address could be put onto a cosmetic Cc: line without
actually appearing on the outgoing envelope, and thus that member would never
receive a copy at all.

And I'd like to point out that Rich has never asked us not to CC the list on
messages to him.

Really, the simple answer for the handful of people who hit the ceiling when
they get a message twice is to point Reply-To: to the list on their own posts.




References:
Indexed By Date Previous: Re: PLEASE DO NOT CC ME ON MESSAGES TO THIS
From: bwarsaw@python.org (Barry A. Warsaw)
Next: Re: PLEASE DO NOT CC ME ON MESSAGES TO THIS
From: Vivek Khera <khera@kcilink.com>
Indexed By Thread Previous: Re: not about (was Re: PLEASE DO NOT CC ME ON MESSAGES TO THIS
From: Chuq Von Rospach <chuqui@plaidworks.com>
Next: Re: PLEASE DO NOT CC ME ON MESSAGES TO THIS
From: "Roger B.A. Klorese" <rogerk@queernet.org>

Google
 
Search Internet Search www.greatcircle.com