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
From: Vivek Khera <khera @ kcilink . com>
Date: Tue, 25 Feb 2003 11:29:01 -0500
To: list-managers @ greatcircle . com
In-reply-to: <15963.28944.963000.741431@gargle.gargle.HOWL>
References: <5.1.0.14.2.20030225052754.4b2fe140@199.74.151.1><15963.28944.963000.741431@gargle.gargle.HOWL>

>>>>> "BAW" == Barry A Warsaw <bwarsaw@python.org> writes:

BAW> Reply-To munging isn't necessary here.  The list s/w can suppress the
BAW> list copy if the member is explicitly mentioned in a recipient header.
BAW> It can also collapse CC headers for subsequent postings.  I'd suspect
BAW> that of those 19, that behavior would be just fine for 18 of them.
BAW> For the others, something like actual MUA support for Mail-Copies-To
BAW> would be sufficient.

I just set up my mail program (VM under XEmacs) to auto-delete
messages with identical Message-ID headers.  It solves this problem
quite nicely, and at much less cost than the bandwidth wasted on this
whole discussion ;-)

No need to rely on MLMs to do it, or on other people's mail programs
doing the right thing...

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.                Khera Communications, Inc.
Internet: khera@kciLink.com       Rockville, MD       +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera   http://www.khera.org/~vivek/


Follow-Ups:
References:
Indexed By Date Previous: Re: PLEASE DO NOT CC ME ON MESSAGES TO THIS LIST
From: "David W. Tamkin" <dattier@panix.com>
Next: Re: PLEASE DO NOT CC ME ON MESSAGES TO THIS
From: bwarsaw@python.org (Barry A. Warsaw)
Indexed By Thread 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: bwarsaw@python.org (Barry A. Warsaw)

Google
 
Search Internet Search www.greatcircle.com