EWSEditor 1.16 Released

I’ve done a lot of clean-up in EWSEditor and added a few needed features for this release. I would like to highlight one major change with EWSEditor in this release: Prior all versions of EWSEditor did not use COM objects. This version uses CDOSYS in order to provide a new feature – the ability to…

0

About: Encrypting or signing a message programmatically

We get cases on encrypting email from time to time.   With Microsoft messaging APIs, sending an encrypted or signed message is not just  matter of flipping flag or pointing to a certificate.  The easiest is going to be using Outlook Object Model (OOM);  however, because of its user tied usage it cannot be used in a…

0

Best Practices - EWS is not generating ATTENDEE section for iCal/MIME/VCALENDAR pulled from a meeting.

This is expected behavior. Per MSDN: Programmatically reestablishing meeting organizer/attendee relationships directly on the appointments is not supported. Calendar POST items do not have attendees per RFC and that’s what is being generated.  What would go into an ATTENDEE section of iCal is a relational point in time thing.  There is an ongoing relationship between a meeting organizer and its attendees…

0

CDOSYS Mailer

CDOSYS is a Windows component which is used to send email by SMTP – similar to its .NET successor System.Net.Mail.  Both of these APIs have their own strengths. Some developers don’t want to use CDOSYS since they want to stick with an all .NET solution.  However, CDOSYS is pretty seasoned is very capable and is…

0

Inline attachments used with EWS and Text, HTML, MHTML or MIME

Exchange Web Services has three different ways to set message body content when working with messages – setting the Text body, setting the html body or creating the message using email MIME (note that there are different types of MIME).  Images which are directly with HTML content are not supported.  HMTLM is an archival format…

1

Howto: Set the organizer of a meeting on the calendar of an attendee using EWS.

I would like to say that this is something which is easily possible – however, I cannot. Setting the organizer directly in code is not supported. Historically, having the organizer over-writable has caused some pretty bad situations for customers. When a meeting is created, the organizer property is automatically hard-stamped and cannot be specified during meeting…

2

Howto: Example to retrieve the body property of a message using the Exchange Managed API.

          public string GetItemMime(ItemId oItemId)         {             string sReturn = string.Empty;             PropertySet oMimePropertySet = new PropertySet(ItemSchema.MimeContent);             Item oItem = Item.Bind(_ExchangeService, oItemId, oMimePropertySet);             return   oItem.MimeContent.ToString() ;                      }           public string GetItemMime(Item oItem)         {             PropertySet oMimePropertySet = new PropertySet(ItemSchema.MimeContent);             oItem.Load(oMimePropertySet);             return oItem.MimeContent.ToString();           }

2

WebStoreExplore 1.8.3 is now public

In the past, the team I belong to has made vailable “super samples” which provide a broad range of coverage-by-example around specific messaging APIs – these are often referred to as API Explorers.  Two examples of these are MFCMAPI (for Extended MAPI) and EWSEditor (Exchange Web Services).  There is a third one which has been used internally for…

1

Don't redistribute product DLLs unless you know its safe and legal to do so.

Redistribution of files in the “C:\Program Files\Microsoft\Exchange Server” folder and sub-folders is not advised/supported.  Yes, this does include the “C:\Program Files\Microsoft\Exchange Server\Public” folder also.  These files are installed when the Exchange 2007 (or later) tools are installed.  If you need these files with the minimal installation, then use the Exchange installer to install them –…

2

Exchange Protocol Documentation

Microsoft released preliminary protocol documentation for Exchange 2007 (as well as Microsoft Office 2007 and SharePoint Server) as part of Microsoft’s Interoperability Principles. The Exchange protocols are now publicly available on the Open Protocol Specifications section of MSDN in preliminary form for developers to review and provide feedback.  You can read more about the announcement…

0