On Sat, May 28, 2005 at 02:14:39PM +0200, Michelle Konzack wrote:
> Same thing with CC (which I can filter) and I hate Bcc!
Filter on message ID then.
Frankly, I love being cc'd on mailing lists. And I never see
duplicates due to the common procmail trick:
:0 Wh: msgid.lock
| formail -D 8192 $HOME/msgid.cache
Not too hard to implement.
There's a few reasons why I like them.
One is that some lists I'm on have a delay -- it's been a while but
d-u has had periods of hours of delay. So the cc allows a response to
come quickly. If I've been working on solving a problem and have to
resort to asking for help on the list it's nice to get the help as
soon as possible. It's a courtesy.
Same as for the person sending the message. If I spend time helping
someone I want that help, as a courtesy to them, to get to them as
soon as possible.
The other is that I (as the receiver) can filter normal list traffic
to a separate mailbox, but cc's to me can, if I choose, go to my main
inbox where I'll see it right away. I realize I can also look at
In-Reply-To: headers, and I do that too. But the cc says that
someone is replying to me, not just to my message.
Finally, I use a mailer that pays attention to Mail-Followup-To:, so
for those that want to try and control what people send (instead of
what they receive ;) I respect that header. On debian-user my
Mail-Followup-To: header includes the list and my own email saying I
do want cc's.
It's a lot easier to control my own setup than the thousands of others
that post on lists I'm on, I find.
Ok, so the cc's do generate extra mail traffic.
--
Bill Moseley
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
