Skip to main content

Sending Attachments via the Exchange Web Services in Exchange 2007

Anyone who has every tried to send an attachment using WebDAV will know that it is a real pain compared with CDOSYS/CDOEX where it was generally just one line of code. The new Exchange Web Services fall somewhere in the middle of these two while not a simple 1 line of code the functionality is there it is just not immediately easy to work out how to do it. Here are two methods I’ve found that work if you want to send a message with an attachment (or just create an item or attach something to an already existing item). Note there are probably some other methods you can use but hopefully this is a little more helpful then just the XML in the current SDK. The first method is to create an item in a folder (eg the drafts folder) using a createitem operation then using the itemid and changeid returned from the create item request use the createattachment operation to attach the file to the new item you created. Then using the new changeid returned after the createattachment operation use a senditem operation to send the Message. The other method is to use a Createitem operation and set the MessageDisposition to SendAndSaveCopy which means the item that is created in this operation will also be sent at the same time. When using this method if you want to send a message with an attachment you need to post a MIME encoded copy of the message you want to send (with the attachment included). To MIME encode a message and its attachments you need to use a MIME Encoder/Parser. While in .NET 2.0 there is the Systen.NET.Mail and MIME classes these namespaces don’t give you direct access to the MIME stream of a message (you can post the message to a local directory and then reopen the file from the file system but this isn’t a very practial method). Fortunalty the good old CDOSYS/CDOEX still makes the best tried and tested MIME parser around and is more the adequate for the task.

I’ve created a couple of C# samples of both methods that use the Webservices proxy object and also a sample for Powershell and VBS that use CDOSYS to get a Base64 encoded version of the MIME Encoded message and then post this XML.

I’ve put a downloadable copy of all the samples here the create,attach send C# sample looks like

using System;
using System.Collections.Generic;
using System.Text;
using System.Net;
using System.IO;
using System.Xml.Serialization;
using ewsCreateAttachSend.mgne12v2;

namespace ewsCreateAttachSend
{
class Program
{
static void Main(string[] args)
{
Program coControlobject = new Program();
ExchangeServiceBinding ewsServiceBinding = new ExchangeServiceBinding();
ewsServiceBinding.Credentials = new NetworkCredential("username", "password", "domain");
ewsServiceBinding.Url = @"https://servername/EWS/exchange.asmx";
MessageType emMessage = new MessageType();
emMessage.Subject = "Test Attachment Send";
emMessage.Body = new BodyType();
emMessage.Body.BodyType1 = BodyTypeType.Text;
emMessage.Body.Value = "Blah,Blah";
emMessage.ItemClass = "IPM.Note";
emMessage.ToRecipients = new EmailAddressType[1];
emMessage.ToRecipients[0] = new EmailAddressType();
emMessage.ToRecipients[0].EmailAddress = "recipient@domain.com";
emMessage.Sensitivity = SensitivityChoicesType.Normal;
ItemIdType iiCreateItemid = coControlobject.CreateDraftMessage(ewsServiceBinding, emMessage);
iiCreateItemid = coControlobject.CreateAttachment(ewsServiceBinding, "c:\\file.ext", iiCreateItemid);
coControlobject.SendMessage(ewsServiceBinding,iiCreateItemid);
}
private ItemIdType CreateDraftMessage(ExchangeServiceBinding ewsServiceBinding,MessageType emMessage) {
ItemIdType iiItemid = new ItemIdType();
CreateItemType ciCreateItemRequest = new CreateItemType();
ciCreateItemRequest.MessageDisposition = MessageDispositionType.SaveOnly;
ciCreateItemRequest.MessageDispositionSpecified = true;
ciCreateItemRequest.SavedItemFolderId = new TargetFolderIdType();
DistinguishedFolderIdType dfDraftsFolder = new DistinguishedFolderIdType();
dfDraftsFolder.Id = DistinguishedFolderIdNameType.drafts;
ciCreateItemRequest.SavedItemFolderId.Item = dfDraftsFolder;
ciCreateItemRequest.Items = new NonEmptyArrayOfAllItemsType();
ciCreateItemRequest.Items.Items = new ItemType[1];
ciCreateItemRequest.Items.Items[0] = emMessage ;
CreateItemResponseType createItemResponse = ewsServiceBinding.CreateItem(ciCreateItemRequest);
if (createItemResponse.ResponseMessages.Items[0].ResponseClass == ResponseClassType.Error)
{
Console.WriteLine("Error Occured");
Console.WriteLine(createItemResponse.ResponseMessages.Items[0].MessageText);
}
else
{
ItemInfoResponseMessageType rmResponseMessage = createItemResponse.ResponseMessages.Items[0] as ItemInfoResponseMessageType;
Console.WriteLine("Item was created");
Console.WriteLine("Item ID : " + rmResponseMessage.Items.Items[0].ItemId.Id.ToString());
Console.WriteLine("ChangeKey : " + rmResponseMessage.Items.Items[0].ItemId.ChangeKey.ToString());
iiItemid.Id = rmResponseMessage.Items.Items[0].ItemId.Id.ToString();
iiItemid.ChangeKey = rmResponseMessage.Items.Items[0].ItemId.ChangeKey.ToString();
}

return iiItemid;
}
private ItemIdType CreateAttachment(ExchangeServiceBinding ewsServiceBinding,String fnFileName,ItemIdType iiCreateItemid) {
ItemIdType iiAttachmentItemid = new ItemIdType();
FileStream fsFileStream = new FileStream(fnFileName, System.IO.FileMode.Open, System.IO.FileAccess.Read);
byte[] bdBinaryData = new byte[fsFileStream.Length];
long brBytesRead = fsFileStream.Read(bdBinaryData, 0, (int)fsFileStream.Length);
fsFileStream.Close();
FileAttachmentType faFileAttach = new FileAttachmentType();
faFileAttach.Content = bdBinaryData;
faFileAttach.Name = fnFileName;
CreateAttachmentType amAttachmentMessage = new CreateAttachmentType();
amAttachmentMessage.Attachments = new AttachmentType[1];
amAttachmentMessage.Attachments[0] = faFileAttach;
amAttachmentMessage.ParentItemId = iiCreateItemid;
CreateAttachmentResponseType caCreateAttachmentResponse = ewsServiceBinding.CreateAttachment(amAttachmentMessage);
if (caCreateAttachmentResponse.ResponseMessages.Items[0].ResponseClass == ResponseClassType.Error)
{
Console.WriteLine("Error Occured");
Console.WriteLine(caCreateAttachmentResponse.ResponseMessages.Items[0].MessageText);
}
else {
AttachmentInfoResponseMessageType amAttachmentResponseMessage = caCreateAttachmentResponse.ResponseMessages.Items[0] as AttachmentInfoResponseMessageType;
Console.WriteLine("Attachment was created");
Console.WriteLine("Change Key : " + amAttachmentResponseMessage.Attachments[0].AttachmentId.RootItemChangeKey.ToString());
iiAttachmentItemid.Id = amAttachmentResponseMessage.Attachments[0].AttachmentId.RootItemId.ToString();
iiAttachmentItemid.ChangeKey = amAttachmentResponseMessage.Attachments[0].AttachmentId.RootItemChangeKey.ToString();
}
return iiAttachmentItemid;
}
private void SendMessage(ExchangeServiceBinding ewsServiceBinding,ItemIdType iiCreateItemid) {
SendItemType siSendItem = new SendItemType();
siSendItem.ItemIds = new BaseItemIdType[1];
siSendItem.SavedItemFolderId = new TargetFolderIdType();
DistinguishedFolderIdType siSentItemsFolder = new DistinguishedFolderIdType();
siSentItemsFolder.Id = DistinguishedFolderIdNameType.sentitems;
siSendItem.SavedItemFolderId.Item = siSentItemsFolder;
siSendItem.SaveItemToFolder = true; ;
siSendItem.ItemIds[0] = (BaseItemIdType)iiCreateItemid;
SendItemResponseType srSendItemReponseMessage = ewsServiceBinding.SendItem(siSendItem);
if (srSendItemReponseMessage.ResponseMessages.Items[0].ResponseClass == ResponseClassType.Error)
{
Console.WriteLine("Error Occured");
Console.WriteLine(srSendItemReponseMessage.ResponseMessages.Items[0].MessageText);
}
else {
Console.WriteLine("Message Sent");
}

}
}
}

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

Downloading a shared file from Onedrive for business using Powershell

I thought I'd quickly share this script I came up with to download a file that was shared using One Drive for Business (which is SharePoint under the covers) with Powershell. The following script takes a OneDrive for business URL which would look like https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filename.txt This script is pretty simple it uses the SharePoint CSOM (Client side object Model) which it loads in the first line. It uses the URI object to separate the host and relative URL which the CSOM requires and also the SharePointOnlineCredentials object to handle the Office365 SharePoint online authentication. The following script is a function that take the OneDrive URL, Credentials for Office365 and path you want to download the file to and downloads the file. eg to run the script you would use something like ./spdownload.ps1 ' https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filena

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.