Export (0) Print
Expand All

Expanding a distribution list by using the EWS Managed API

EWS Managed API

You can use the Microsoft Exchange Web Services (EWS) Managed API to expand a distribution list to display all members.

Last modified: October 13, 2012

Applies to: EWS Managed API | Exchange Server 2007 Service Pack 1 (SP1) | Exchange Server 2010

Note: This content applies to the EWS Managed API 2.0 and earlier versions. For the latest information about the EWS Managed API, see Web services in Exchange.

To expand a distribution list

  1. Instantiate the ExpandGroupResults object by calling the ExpandGroup method of an ExchangeService object named service.

    ExpandGroupResults myGroupMembers = service.ExpandGroup("mygroup@contoso.com");
  2. Display the expanded list of group members.

    // Display the group members.
    foreach (EmailAddress address in myGroupMembers.Members)
         Console.WriteLine("Email Address: {0}", address);

The following example shows how to return and display group members in a distribution list.

private static void ExpandDistributionLists(ExchangeService service)
     // Return the expanded group.
     ExpandGroupResults myGroupMembers = service.ExpandGroup("Group1@contoso.com");

     // Display the group members.
     foreach (EmailAddress address in myGroupMembers.Members)
         Console.WriteLine("Email Address: {0}", address);

The following example shows the XML that is sent by using the ExpandGroup method.

<?xml version="1.0" encoding="utf-8"?>
  <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <t:RequestServerVersion Version="Exchange2010_SP1" />

The following example shows the XML that is returned by the ExpandGroup method.

<?xml version="1.0" encoding="utf-8"?>
  <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
      <h:ServerVersionInfo MajorVersion="14" MinorVersion="1" MajorBuildNumber="225" MinorBuildNumber="71" Version="Exchange2010_SP2" xmlns:h="http://schemas.microsoft.com/exchange/services/2006/types" xmlns="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
    <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <m:ExpandDLResponse xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types">
          <m:ExpandDLResponseMessage ResponseClass="Success">
            <m:DLExpansion TotalItemsInView="2" IncludesLastItemInRange="true">
                <t:Name>Brian Smith</t:Name>
                <t:Name>Karim Manar</t:Name>

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(String) 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.

© 2014 Microsoft