Wcf ExchangeServiceBinding、EWS、Exchange Web服务

目前我在尝试使用EWS时遇到了一个问题，最初的要求是连接到特定用户的邮件，然后搜索特定文件夹，搜索邮件，然后将附件下载到特定文件夹到本地计算机，以便以后可以由Integration Services处理，我不想使用EWS托管API，因为我不想在迁移到生产服务器时安装任何东西，现在我的想法是开发一个WCF服务，该服务通过.asmx uri连接到EWS服务，并且能够满足我的要求，现在我可以连接到公司的EWS，但我有一些疑问：

根据微软的说法：他们说你必须为你的项目添加一个web服务引用，虽然它只提到VS 2005和VS 2008，但我正在使用VS 2012，它应该自动创建ExchangeServiceBinding类，该类为你提供模拟帐户所需的一切，我的第一个问题是：为什么我没有看到这个类添加到我的项目中？我是否应该认为这是因为我使用的是VS 2012

好的，无论如何，我可以使用一些方法，比如getPasswordExpirationTime，但是当我使用FindFolder方法时，我得到了一个错误：帐户没有权限模拟请求的用户。这是我的方法：

using (ExchangeServicePortTypeClient exchangeServicePortTypeClient = new ExchangeServicePortTypeClient())
                {
                    exchangeServicePortTypeClient.ChannelFactory.Endpoint.Address = new EndpointAddress("https://email.kraft.com/EWS/Exchange.asmx");


                    FindFolderResponseType findFolderResponseType = null;

                    exchangeServicePortTypeClient.FindFolder(
                        new ExchangeImpersonationType
                        {
                            ConnectingSID = new ConnectingSIDType
                            {
                                Item = @"gilberto.gutierrez@mdlz.com",
                                ItemElementName = ItemChoiceType1.PrimarySmtpAddress
                            }
                        },
                        null,
                        new RequestServerVersion { Version = ExchangeVersionType.Exchange2010_SP2 },
                        null,
                        new FindFolderType
                        {
                            FolderShape = new FolderResponseShapeType
                            {
                                BaseShape =
                                  DefaultShapeNamesType.Default
                            }
                        }, out findFolderResponseType);

                }                   

我已尝试通过以下方式设置凭据：

exchangeServicePortTypeClient.ClientCredentials.Windows.ClientCredential.UserName
exchangeServicePortTypeClient.ClientCredentials.Windows.ClientCredential.Password      
exchangeServicePortTypeClient.ClientCredentials.Windows.ClientCredential.Domain             
exchangeServicePortTypeClient.ChannelFactory.Credentials.Windows.ClientCredential.UserName
exchangeServicePortTypeClient.ChannelFactory.Credentials.Windows.ClientCredential.Password
exchangeServicePortTypeClient.ChannelFactory.Credentials.Windows.ClientCredential.Domain

没有运气：

顺便说一下，这是我的wcf配置文件

<?xml version="1.0" encoding="utf-8"?>

<configuration>

    <!--Diagnostics section, we will only catch error and warning in production-->

    <system.diagnostics>
        <sources>
            <source propagateActivity="true" name="System.ServiceModel" switchValue="Error, Warning">
                <listeners>
                    <add type="System.Diagnostics.DefaultTraceListener" name="Default">
                        <filter type="" />
                    </add>
                    <add type="System.Diagnostics.DefaultTraceListener" name="SellOut.ExchangeWcfService">
                        <filter type="" />
                    </add>
                    <add name="ServiceModelTraceListener">
                        <filter type="" />
                    </add>
                </listeners>
            </source>
            <source name="System.ServiceModel.MessageLogging" switchValue="Error, Warning">
                <listeners>
                    <add type="System.Diagnostics.DefaultTraceListener" name="Default">
                        <filter type="" />
                    </add>
                    <add type="System.Diagnostics.DefaultTraceListener" name="SellOut.ExchangeWcfService">
                        <filter type="" />
                    </add>
                    <add name="ServiceModelMessageLoggingListener">
                        <filter type="" />
                    </add>
                </listeners>
            </source>
        </sources>
        <sharedListeners>
            <add initializeData="C:\Users\LFH2623\Documents\SellOut\SellOut\SellOut.Hosts.ExchangeWcfService\SellOut.ExchangeWcfService_web_tracelog.svclog"
              type="System.Diagnostics.XmlWriterTraceListener, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
              name="ServiceModelTraceListener" traceOutputOptions="LogicalOperationStack, DateTime, Callstack">
                <filter type="" />
            </add>
            <add initializeData="C:\Users\LFH2623\Documents\SellOut\SellOut\SellOut.Hosts.ExchangeWcfService\SellOut.ExchangeWcfService_web_messages.svclog"
                type="System.Diagnostics.XmlWriterTraceListener, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
                name="ServiceModelMessageLoggingListener" traceOutputOptions="LogicalOperationStack, DateTime, Callstack">
                <filter type="" />
            </add>
        </sharedListeners>
        <trace autoflush="true" />
    </system.diagnostics>

    <!--Framework Section-->

    <appSettings>
        <add key="aspnet:UseTaskFriendlySynchronizationContext" value="true" />
    </appSettings>  

    <!--Web section-->

    <system.web>        
        <compilation debug="true" targetFramework="4.5" />
        <httpRuntime targetFramework="4.5" maxRequestLength="2147483646" />
    </system.web>

    <!--Web server section-->

    <system.webServer>
        <directoryBrowse enabled="false"/>
        <defaultDocument enabled="true"/>               
        <modules runAllManagedModulesForAllRequests="true"/>
    </system.webServer>

    <!--WS section-->

    <system.serviceModel>

        <diagnostics>
            <messageLogging logMalformedMessages="true"
                            maxMessagesToLog="10000"
                            logMessagesAtTransportLevel="true"
                            logMessagesAtServiceLevel="True"
                            logEntireMessage="true"/>
            <endToEndTracing activityTracing="false" />
        </diagnostics>

        <!--For the ExchangeWebService we will aply the following service and endpoint behaviors-->

        <behaviors>

            <serviceBehaviors>
                <behavior name="ExchangeWebService">
                    <serviceMetadata httpGetEnabled="true" httpsGetEnabled="false" />
                    <serviceDebug includeExceptionDetailInFaults="false" httpHelpPageEnabled="true" />
                    <dataContractSerializer maxItemsInObjectGraph="2147483646" />
                    <serviceTimeouts transactionTimeout="01:00:00" />
                    <serviceThrottling maxConcurrentCalls="100" maxConcurrentSessions="100" maxConcurrentInstances="100"/>
                    <serviceDiscovery>
                        <announcementEndpoints>
                            <endpoint kind="udpAnnouncementEndpoint"></endpoint>
                        </announcementEndpoints>
                    </serviceDiscovery>
                </behavior>             
            </serviceBehaviors>

            <!-- Define the corresponding scope for the clients to find the service through resolve message -->

            <endpointBehaviors>
                <behavior name="ExchangeWebService">
                    <endpointDiscovery enabled="true">
                        <scopes>
                            <add scope="http://SellOut.ExchangeWcfService/"/>
                        </scopes>
                    </endpointDiscovery>
                </behavior>
            </endpointBehaviors>

        </behaviors>

        <!-- In case you want to scale this service -->

        <standardEndpoints>

            <!-- We allow the service to be discoverable through the network in an adhoc architecture through UDP -->

            <udpDiscoveryEndpoint>
                <standardEndpoint name="adhocDiscoveryEndpointConfiguration"
                                  discoveryMode="Adhoc"
                                  discoveryVersion="WSDiscovery11"
                                  maxResponseDelay="00:00:10">
                </standardEndpoint>
            </udpDiscoveryEndpoint>

            <!-- We allow the service to be discoverable through the network in a managed architecture -->

            <discoveryEndpoint>
                <standardEndpoint name="managedDiscoveryEndpoint" discoveryMode="Managed" maxResponseDelay="00:01:00"/>
            </discoveryEndpoint>

            <!-- We announce the service with hello & bye -->

            <announcementEndpoint>
                <standardEndpoint name="udpAnnouncementEndpointConfiguration"
                                  discoveryVersion="WSDiscovery11" />
            </announcementEndpoint>

        </standardEndpoints>

        <!--All the Kraft's clients are .net, so we will use the proprietary binary message encoding to reduce the message's size -->

        <bindings>
            <customBinding>
                <binding name="wsHttpBindingBynaryEncoding"
                         closeTimeout="00:10:00"
                         openTimeout="00:10:00"
                         receiveTimeout="00:10:00"
                         sendTimeout="00:10:00">
                    <binaryMessageEncoding>
                        <readerQuotas maxDepth="32"
                                      maxStringContentLength="5242880"
                                      maxArrayLength="2147483646"
                                      maxBytesPerRead="4096"
                                      maxNameTableCharCount="5242880" />
                    </binaryMessageEncoding>
                    <httpTransport
                                    transferMode="Buffered"
                                    maxBufferPoolSize="2147483646"
                                    maxReceivedMessageSize="2147483646">
                    </httpTransport>
                </binding>
            </customBinding>

            <basicHttpBinding>
                <binding name="KraftEWS" messageEncoding="Text" transferMode="Buffered">
                    <security mode="Transport">
                        <transport clientCredentialType="Windows" proxyCredentialType="Windows"></transport>                        
                    </security>             
                </binding>
            </basicHttpBinding>

        </bindings>

        <!-- We reference the Kraft EWS -->

        <client>
            <endpoint binding="basicHttpBinding" bindingConfiguration="KraftEWS"
                      contract="KraftEWS.ExchangeServicePortType"                                     
                      name="ExchangeServiceBinding_ExchangeServicePortType">                
            </endpoint>
        </client>

        <!--Services section-->

        <services>
            <service name="SellOut.Services.Exchange.ExchangeWebService" behaviorConfiguration="ExchangeWebService">
                <endpoint name="rules"
                          address="rules"
                          binding="customBinding"
                          bindingConfiguration="wsHttpBindingBynaryEncoding"
                          behaviorConfiguration="ExchangeWebService"
                          contract="SellOut.Contracts.Exchange.IExchangeRulesContract"/>
                <endpoint name="udpDiscovery"
                          kind="udpDiscoveryEndpoint"
                          endpointConfiguration="adhocDiscoveryEndpointConfiguration" />
                <endpoint name="mex"
                          address="mex"
                          binding="mexHttpBinding"
                          contract="IMetadataExchange" />               
            </service>
        </services>

        <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />

    </system.serviceModel>

</configuration>

另一件需要提及的事情是，在此配置中：

<basicHttpBinding>
                    <binding name="KraftEWS" messageEncoding="Text" transferMode="Buffered">
                        <security mode="Transport">
                            <transport clientCredentialType="Windows" proxyCredentialType="Windows"></transport>                        
                        </security>             
                    </binding>
                </basicHttpBinding>

如果我删除部分客户端凭据类型Windows，则在尝试运行服务时，异常为：

HTTP请求未经客户端身份验证方案“匿名”授权。从服务器接收的身份验证标头为“协商，NTLM”

你们能帮我一下吗

---

谢谢您的建议。

我强烈建议您为此使用EWS管理的API。我不明白你说你不想在生产服务器上安装任何东西是什么意思，因为你必须在生产服务器上安装WCF服务，以及Add Web service reference项目创建的对象模型。但是，看起来你通过了这个部分，所以让我们继续

很好，很高兴知道您可以调用GetPasswordExpirationTime。谢谢你给我提供的信息

您收到该帐户无权模拟请求用户的消息的原因是，运行WCF服务的帐户没有邮箱的模拟权限。在您的服务帐户可以访问用户帐户之前，您将需要执行以下操作。一旦您的服务具有Exchange可以在AD中查找的凭据，并且它有权模拟您的待办事项列表中的用户，您的代码就应该可以工作，因为身份验证是基于服务帐户的身份完成的

代码示例之后的问题的所有部分都不在范围内。您不需要对web.config进行任何更改，至少我不这么认为。我假设您正在对一个内部部署服务器进行测试，因为身份验证方案是协商和NTLM

关于,

---

你链接到的文章

谢谢你的回复Michael，在服务器上安装任何东西我的意思是我不想在服务器上安装EWS API，服务器已经安装了.NET framework 4.5，因此我们可以假设Wcf可以正常工作。我还想告诉您，我发现了问题，exchangeservicebinding类不是自动创建的，因为您必须像添加旧服务引用一样添加服务引用，我的意思是，单击“高级属性”，然后添加web引用，因此，通过这个类，我可以连接指定我想要的任何凭据，而无需模拟。Michael，您关于Exchange中模拟的说法是正确的，是的，身份验证方案是协商和NTLM，非常感谢Mike。