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

Testing and Sending email via SMTP using Opportunistic TLS and oAuth in Office365 with PowerShell

As well as EWS and Remote PowerShell (RPS) other mail protocols POP3, IMAP and SMTP have had OAuth authentication enabled in Exchange Online (Official announcement here ). A while ago I created  this script that used Opportunistic TLS to perform a Telnet style test against a SMTP server using SMTP AUTH. Now that oAuth authentication has been enabled in office365 I've updated this script to be able to use oAuth instead of SMTP Auth to test against Office365. I've also included a function to actually send a Message. Token Acquisition  To Send a Mail using oAuth you first need to get an Access token from Azure AD there are plenty of ways of doing this in PowerShell. You could use a library like MSAL or ADAL (just google your favoured method) or use a library less approach which I've included with this script . Whatever way you do this you need to make sure that your application registration  https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-
Read more

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 Graph is limited to a m
Read more

How to test SMTP using Opportunistic TLS with Powershell and grab the public certificate a SMTP server is using

Most email services these day employ Opportunistic TLS when trying to send Messages which means that wherever possible the Messages will be encrypted rather then the plain text legacy of SMTP.  This method was defined in RFC 3207 "SMTP Service Extension for Secure SMTP over Transport Layer Security" and  there's a quite a good explanation of Opportunistic TLS on Wikipedia  https://en.wikipedia.org/wiki/Opportunistic_TLS .  This is used for both Server to Server (eg MTA to MTA) and Client to server (Eg a Message client like Outlook which acts as a MSA) the later being generally Authenticated. Basically it allows you to have a normal plain text SMTP conversation that is then upgraded to TLS using the STARTTLS verb. Not all servers will support this verb so if its not supported then a message is just sent as Plain text. TLS relies on PKI certificates and the administrative issue s that come around certificate management like expired certificates which is why I wrote th
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.