Wednesday 24 March 2010
Fun With BCC
Luis Villa falls into the old "reply to all on a BCCed email" trap...
I think it's safe to tell a little story about the best case I was involved with. When I was finishing up my PhD in 2000, Jim Larus at Microsoft Research asked me to come up for a visit so they could encourage me to apply for a job there. I declined, carefully and politely explaining that I'd already decided I did not want to work at Microsoft (because of the issues around the company as a whole; MSR was fantastic and I liked the people there). I BCC'ed my PhD advisors on this reply because they needed to be aware of the situation. One of my advisors replied "Stick it to 'em!" ... to all, of course. Hilarity all around.
BCC is a dangerous and obsolete tool IMHO. It's safer to just forward your message to the secret recipients.
Comments
Could the email client help here?
It could automatically adjust the headers for BCC recipients, so that reply-all doesn't get sent to anyone but the sender.
It could disallow/doublecheck for reply-all on BCC-received messages.
And, it could make it easier to forward a sent message (e.g. Cmd+Shift+L forward last sent message).
Oh yeah, and also, when you press preview, the input boxes aren't repopulated. But that's not what I'm talking about.
Consider the case where a person starts a thread to someone who then replies, but copies a new contact who is better suited to continue the conversation. The person who started the thread can now move the recipients on the thread who are no longer necessary so they don't receive spam.
But, the beauty of this tactic is that those initial recipients can still see that last message to ensure that the hand off was made and see where the conversation is heading before sign-off. If they choose, they can re-enter the conversation by replying and asking not to be bcc-ed.
This blog post has more writing about this use case:
http://www.bothsidesofthetable.com/2010/03/02/im-moving-you-to-bcc/