Re: Private copies of list replies (Was: Re: buildd and experimental)
- To: email@example.com
- Subject: Re: Private copies of list replies (Was: Re: buildd and experimental)
- From: "John H. Robinson, IV" <firstname.lastname@example.org>
- Date: Wed, 1 Mar 2006 09:48:45 -0800
- Message-id: <20060301174843.GA11185@ucsd.edu>
- Mail-followup-to: email@example.com
- In-reply-to: <firstname.lastname@example.org>
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <20060228111352.GA30813@boogie.lpds.sztaki.hu> <email@example.com> <20060301014601.GE22487@boogie.lpds.sztaki.hu> <firstname.lastname@example.org>
Brian M. Carlson wrote:
> Mutt has several different reply options, some of them may be more
> appropriate than others. Anyway, it does not matter: the Debian Mailing
> List Code of Conduct *explicitly* 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
> As the sender, it is your job to comply with that, not mine as the
As the sender, it is your job to communicate this effectively. Relying
upon headers that you are not in your control over is a poor way to
attempt to communicate this. Majordomo understood this, and had all
mailing list commands be set in the *body*, the only part that was under
control of the sender.
If you use a header that is commonly not seen by a mailer, such as
X-Please: cc me
that will similarly probably end in dissapointment.
In the signature would probably be poor, as the lowlighting would hide
it, and who really reads the signatures, anyway? The best place is
probably right before the signature. A simple one line things: Please cc
me, I am not subscribed to the list.
I speak from my own personal experience. I keep my mailer set to show me
no headers whatsoever. I get the information I need most of the time
from the index. This includes From:, Subject:, and Date:. That is it.
When I did have my mailer show me headers, that was all I had it show
anyway. I never look at X- headers, nor *Spam* headers. They are
I will happily comply with wishes, but they have to be communicated
in a way I can understand. I don't think I am alone in this, either.
John H. Robinson, IV email@example.com
WARNING: I cannot be held responsible for the above, sbih.org ( )(:[
as apparently my cats have learned how to type. spiders.html ((((