- A step-by-step screenshot tutorial for automatically BCCing an email address for all outgoing Outlook messages.
- From Outlook 2007 to Outlook 2010, Microsoft removed the BCC field. We’ll show you how to add the BCC field back in.
- To auto BCC in Outlook, we’ll need to show the developer tab and add a script.
- See the comments for how to set up an automatic BCC for messages sent only from a particular email address (for multiple Outlook accounts—thanks, Nathan!)
Perhaps it was due to one too many passive aggressive intra-office stealth BCCs (Blind Carbon Copy.) But seriously, for some reason, Microsoft decided to roll back access to BCCs in Office 2010. For one, the new message dialog doesn’t even have a BCC field. But you also can’t set up Outlook 2010 rules to automatically BCC someone (although you can set up a rule to automatically CC a message.) For my purposes, this is kind of a pain. I am a Gmail/Outlook hybrid user (I have about three different email addresses, each for a different purpose) and I like to keep all of my messages archived in my main Gmail account for easy reference. So, what I wanted was a way to forward all of my sent messages to my Gmail account (I already have all incoming messages forwarded there by a server-side rule.) Easier said than done but I think I’ve figured out the easiest way.
It turns out that there are three things to be done to unlock the full potential of BCC in Outlook 2010:
- Show the BCC Field in the New Email window.
- Reveal the Developer ribbon.
- Add some custom Visual Basic code.
It’s not as complicated as it seems. But let’s move through these three from easiest to hardest.
(Note: You can also buy third-party Add-Ins for Outlook 2010 that do this—but I’d recommend this method. It’s free.)
Show the BCC Field in New Emails in Outlook 2010
Launch Outlook 2010.
Click the New Email button. In the message composition window, click the Options tab.
Click the BCC button. This action reveals the BCC field. Henceforth, you shall have access to the BCC field in all future Outlook 2010 emails. If you get tired of the extra space it takes up, just click it again to be rid of it.
Now, you can use the BCC field for one-offs. But what if you wanted to automatically BCC yourself (or someone else) on every outgoing message? To do this, follow the steps below.
Display the Developer Ribbon
I’m basing this how-to on a great bit of custom Visual Basic code written by Michael Kizer. Michael wrote this VBA snippet for Outlook 2007, but it works for Outlook 2010. The only problem: it’s a bit tough to find Visual Basic Editor in Outlook 2010. It’s hiding in the Developer ribbon, which, by default, is hidden from view. Here’s how to enable it:
Launch Outlook 2010.
Click the File tab and choose Options.
Click Customize Ribbon on the left-hand panel. Now, in the list on the far right, make sure Developer is checked. Click OK.
The Developer tab will now be revealed in your Outlook 2010 ribbon.
Automatically BCC Outgoing Messages in Outlook 2010
Now, it’s time to add the code that Mr. Kizer put together.
Go to the Developer tab and click Visual Basic.
On the left, expand Project1 (VbaProject.OTM to reveal Microsoft Outlook Objects. Expand Microsoft Outlook Objects and then double-click ThisOutlookSession.
In the code editor window, choose Application from the drop-down menu in the top-left.
In the top-left drop-down menu, choose ItemSend.
Position your cursor after “Private Sub Application_ItemSend(ByVal Item As Object, Cancel As Boolean)” and before “End Sub.” Now, copy and paste the following between those two lines.
Dim objRecip As Recipient Dim strMsg As String Dim res As Integer Dim strBcc As String On Error Resume Next ' #### USER OPTIONS #### ' address for Bcc -- must be SMTP address or resolvable ' to a name in the address book strBcc = "SomeEmailAddress@domain.com" Set objRecip = Item.Recipients.Add(strBcc) objRecip.Type = olBCC If Not objRecip.Resolve Then strMsg = "Could not resolve the Bcc recipient. " & _ "Do you want still to send the message?" res = MsgBox(strMsg, vbYesNo + vbDefaultButton1, _ "Could Not Resolve Bcc Recipient") If res = vbNo Then Cancel = True End If End If Set objRecip = Nothing
Look for the line that reads: strBcc=”SomeEmailAddress@domain.com” and replace it with the email address you’d like to BCC for SomeEmailAddress@domain.com. For example, swap it out for email@example.com or firstname.lastname@example.org.
Don’t forget to save the changes. Close the Visual Basic Editor and return to Outlook.
Now, when you send messages from Outlook 2010, they’ll be automatically BCC’d to the recipient you chose in the Visual Basic editor. You don’t have to type their name in the BCC field, nor will you even see it entered into the BCC field since the Visual Basic script kicks in after you hit send. (A handy tip for any cyber spies.)
And there you have it.
Filtering BCC’d Gmail Messages
One last thing to note: if you are using this to build a Gmail archive, I recommend using a customized Gmail address with something like +bcc appended to it. However, since the address won’t show up in the to: field, you can’t filter it out like normal. So, instead, you’ll have to use the “deliveredto:” string in Gmail. For example, I’d use “deliveredto: email@example.com” and then set up a rule that automatically archives these messages and marks them as read.
A Note About Macro Security
Note: This section may help those who find that the macro stops working the next day or after a system restart.
To get this to work, you may need to alter your macro security settings. Either way, you’ll probably get a nagging message like this when Outlook 2010 launches:
As you can see, that just refers to the script that you put into ThisOutlookSession—it doesn’t mean you have a virus. You can click Enable Macros to proceed with your Auto BCC script intact.
If you want to skip this step, you can change your Macro Security settings by going to the Developer tab and clicking Macro Security.
Under “Macro Settings,” you’ll have a few different options:
For a nag-free existence, choose “Enable all macros,” though this is, of course, potentially dangerous. The real solution here is to get your macro digitally signed—but that’s a bit of an involved process, which I’ll go over in another post (How to Create a Self-Signed Digital Certificate in Microsoft Office 2010). Stay tuned!