Skip to main content

To:, Cc: and Bcc:

Occasionally, I get an e-mail that makes me think people are confused by these 3 features of e-mail. For example, someone will send out an e-mail that clearly meant for a single person but they'll put everybody in the To: field. How do I know the e-mail is meant for that person...because the opening salutation ends in the person's name (for example: "Hello Kevin" or "hey John", or simply "Jack"). If the e-mail is meant solely for Kevin, why include everyone in the To field (unless you are trying to rat out the recipient)?

To be clear, this is how you use these fields:
  • To: Include the primary recipient(s)
  • Cc: Include the secondary recipient(s). There's no expectation that these guys will respond. It's just a courtesy notification. Say you want to applaud a team member by writing an e-mail to his/her boss. You Cc him/her so he/she is aware but is not expected to respond.
  • Bcc: This should be obvious. If you are in the Bcc, you should never never hit "Reply All" since the other recipients don't know you got the e-mail in the first place. This is what you do when you want to CYA (perhaps you have a co-worker that lies about not receiving e-mail...send it and Bcc his/her boss).
BTW: Cc means Carbon Copy and Bcc means Blind Carbon Copy. Those terms are from the days of typewriters and carbon papers.

Got it now? Oh one last thing, when you are forwarding jokes to a bunch of people, most of whom don't know one another, do not put everyone's email address in the To field. That's just totally inappropriate.

Comments

Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology.

InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options:

convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations)use one of Al Gore's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously. You'll need every bit of time you can get.
quit immediately while you still have your sanityFirst, InfoPath:

To me InfoPath is like programming in assembly language. Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button:

in most technology: buttonA.enabled = false (or something similar).

In InfoPath, you simply can't do this.…

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said:
InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... (more)Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A horri…

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design.
For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial sou…