Applying conversation actions by using the EWS Managed API

1. Instantiate a class that implements the IEnumerable interface that iterates a collection of strings. Add categories to the enumerator.

   C#

   Copy

   List<string> categories = new List<string>();
   categories.Add("Customer");
   categories.Add("System Integrator");
   

2. Call the EnableAlwaysCategorizeItems method with the category enumerator.

   C#

   Copy

   conversation.EnableAlwaysCategorizeItems(categories, true);
   

3. Call the EnableAlwaysMoveItems method with the identifier of the folder that will contain the moved items.

   Copy

   conversation.EnableAlwaysMoveItems(WellKnownFolderName.Drafts, false);
   

The following example shows how to add categories to existing items in a conversation and apply the same categories to future items in the conversation. It also shows how to enable the automatic moving of items in the conversation to a folder; in this example, items are moved to the Drafts folder.

static void ApplyConversationActions(ExchangeService service, Conversation conversation)
{
   // Create a list of categories to apply to a conversation.
   List<string> categories = new List<string>();
   categories.Add("Customer");
   categories.Add("System Integrator");

   // Apply categorization to all items in the conversation and process the request
   // synchronously after enabling this rule and all item categorization has been applied. 
   // This results in a call to EWS. 
   conversation.EnableAlwaysCategorizeItems(categories, true);

   // Apply an always move rule to all items in the conversation and move the items
   // to the Drafts folder. Process the request asynchronously and return the response. 
   // immediately. This results in a call to EWS. 
   conversation.EnableAlwaysMoveItems(WellKnownFolderName.Drafts, false);
}

For information about compiling this code, see Getting started with the EWS Managed API.

• Write appropriate error handling code for common search errors.
  
• Review the client request XML that is sent to the Exchange server.
  
• Review the server response XML that is sent from the Exchange server.
  
• Set the service binding as shown in Setting the Exchange service URL by using the EWS Managed API. Do not hard code URLs because if mailboxes move, they might be serviced by a different Client Access server. If the client cannot connect to the service, retry setting the binding by using the AutodiscoverUrl method.
  
• Set the target Exchange Web Services schema version by setting the requestedServerVersion parameter of the ExchangeService constructor. For more information, see Versioning EWS requests.
  

• Use HTTP with SSL for all communication between client and server.
  
• Always validate the server certificate that is used for establishing the SSL connections. For more information, see Validating X509 certificates.
  
• Do not include user names and passwords in trace files.
  
• Verify that Autodiscover lookups that use HTTP GET to find an endpoint always prompt for user confirmation; otherwise, they should be blocked.
  

Tasks