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

Export calendar Items to a CSV file using EWS and Powershell

Somebody asked about this last week and while I have a lot of EWS scripts that do access the Calendar I didn't have a simple example that just exported a list of the Calendar events with relevant information to a CSV file so here it is.

I've talked on this one before in this howto  but when you query the calendar folder using EWS you need to use a CalendarView which will expand any recurring appointments in a calendar. There are some limits when you use a calendarview in that you can only return a maximum of 2 years of appointments at a time and paging will limit the max number of items to 1000 per call. So if you have a calendar with a very large number of appointments you need to break your query into small date time blocks. In this example script I'm just grabbing the next 7 days of appointments if you want to query a longer period you need to adjust the following lines (keeping in mind what I just mentioned)

#Define Date to Query
$StartDate = (Get-Date)
$EndDate = (Ge…

EWS Managed API and Powershell How-To series Part 1

I thought I'd start the year with a series of posts that goes back over the basics of using the EWS Managed API from Powershell and provides a modular remarked example that you can easily cut and paste to build your own scripts. Along the way in this series I'll show a whole bunch of examples around specific things.

As a starting point for versions this will be Powershell Version 2.0  and the EWS Managed API 1.1 (which will soon change to 1.2 once released) http://www.microsoft.com/download/en/details.aspx?id=13480.

The starting point for any EWS script your going to write is connecting to Exchange for which there are three important pieces of information you will need. Firstly you need to know the version of Exchange your running in this script its going to be held in the following variable

$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP1

Other valid values for Exchange 2007 would be

$ExchangeVersion = [Microsoft.Exchange.WebServices.…

Writing a simple scripted process to download attachmentts in Exchange 2007/ 2010 using the EWS Managed API

Every complicated thing in life is made up of smaller simpler building blocks, when it comes to writing a script (or any code really) the more of these little building blocks you have to figure out the more the process of solving a problem can become bewildering. The Internet generally provides you with lots of half eaten sandwiches of information something someone else has taken a bite out but a lot of the time half done, and as with any code its usefulness declines over time as new and better API's and methods are derived. In this post I'm going to go through a simple scripted process that hopefully covers a few more of these smaller building blocks that you might face when asked to come up with a simple costless solution to perform an automated business function with a script.

So the process im going to look at is one that comes up a lot and that is you have an Email that comes into to certain mailbox every day with a certain subject in my case "Daily Export" this …
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.