Skip to main content

BCC's with CDOEX

This one pops up now and again and can be a little bit of a pain to deal with in CDOEX. In the good old days of CDO 1.2 you could access the recipients collection of an email directly but with CDOEX you can't really do this, you only have a few properties which you can access. On a message the BCC field is an envelope field that you usually don't really care too much about, but when it comes to tasks and meeting requests the BCC field takes on a new perspective. In a task the BCC fields gets used for the StatusOnCompletionRecipients which controls who gets a task completion messages when a task is marked as complete and in a Meeting the BCC field is the resources field.

With meeting requests and appointments you can access the recipients collection via the IAttendees interface. So to add a BCC some code like this will work

Set appt = CreateObject("CDO.Appointment")
Set Atnd = Appt.Attendees.Add
Atnd.Address = "resource@yourdomain.com"
Atnd.Role = 2
Atnd.Type = "resource"

For a task you can't really do this but one way around this if you are creating a task (remembering that tasks aren't really supported in CDOEX anyway) is to first create a appointment add the number of people you want to the BCC and CC and then flip the messageclass and davcontent class values and save the item as a task. The only drawback with this method is you end up with a lot of redundant message properties and it only works on creation.

Set appt = CreateObject("CDO.Appointment")
Set Atnd = Appt.Attendees.Add
Atnd.Address = "completionnotify@domain.com"
Atnd.Role = 2
Atnd.Type = "resource"
Set Atnd1 = Appt.Attendees.Add
Atnd1.Address = "updatelist@domain.com"
Atnd1.Role = 1
Atnd1.Type = "Individual"
with appt
.Fields("DAV:contentclass").Value = "urn:content-classes:task"
.Fields("http://schemas.microsoft.com/exchange/outlookmessageclass").Value = "IPM.Task"
.Fields("urn:schemas:mailheader:subject").Value = "Test Task"
.Fields("urn:schemas:httpmail:textdescription").Value = "Blah"
.Fields("http://schemas.microsoft.com/mapi/proptag/0x82D9000B").Value = false
.Fields("http://schemas.microsoft.com/mapi/proptag/0x82BF0005").Value = 0
.Fields("http://schemas.microsoft.com/mapi/proptag/0x82C00003").Value = 0
.Fields("http://schemas.microsoft.com/mapi/proptag/0x82670003").Value = 0
.Fields("http://schemas.microsoft.com/mapi/proptag/0x82C00003").Value = 0
.Fields("http://schemas.microsoft.com/mapi/proptag/0x82C10003").Value = 0
.Fields.update
.datasource.saveto "file://./backofficestorage/yourdoain.com/mbx/mailbox/tasks/taskurl.eml"
end with
 
A better way to handle this might be to use WebDAV which is not inhibited in the same way in regards to BCC's.

Popular posts from this blog

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Gr...
Read more

Exporting and Uploading Mailbox Items using Exchange Web Services using the new ExportItems and UploadItems operations in Exchange 2010 SP1

Two new EWS Operations ExportItems and UploadItems where introduced in Exchange 2010 SP1 that allowed you to do a number of useful things that where previously not possible using Exchange Web Services. Any object that Exchange stores is basically a collection of properties for example a message object is a collection of Message properties, Recipient properties and Attachment properties with a few meta properties that describe the underlying storage thrown in. Normally when using EWS you can access these properties in a number of a ways eg one example is using the strongly type objects such as emailmessage that presents the underlying properties in an intuitive way that's easy to use. Another way is using Extended Properties to access the underlying properties directly. However previously in EWS there was no method to access every property of a message hence there is no way to export or import an item and maintain full fidelity of every property on that item (you could export the...
Read more

EWS Create Mailbox folder Powershell module for Exchange and Office365 Mailboxes

This is a rollup post for a couple of scripts I've posted in the past for creating folders using EWS in an Exchange OnPremise or Exchange online Cloud mailbox. It can do the following Create a Folder in the Root of the Mailbox Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test Create a Folder as a SubFolder of the Inbox Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test -ParentFolder '\Inbox' Create a Folder as a SubFolder of the Inbox using EWS Impersonation Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test -ParentFolder '\Inbox' -useImpersonation Create a new Contacts Folder as a SubFolder of the Mailboxes Contacts Folder Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test -ParentFolder '\Contacts' -FolderClass IPF.Contact Create a new Calendar Folder as a SubFolder of the Mailboxes Calendar Folder Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test -Parent...
Read more
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.