I'm planning to migrate my company's email system from Zimbra opensource to the network edition.
For the time being I'm using the NE trial on a VM for testing purposes trying to get the EWS protocol work.
The main point to this migration is to only use EWS for each email client we have in the company [i.e. outlook 2016, mac or windows, thunderbird with exquilla...] (but not use Exchange $$$
)I've installed a fresh 8.8.12 version and everything seems to work properly (I don't try for the time being to send emails that's not the point of my tests)
Autodiscover seems ok, EAS is OK but it's impossible to have EWS works.
When I use https://testconnectivity.microsoft.com to test connectivity everything is ok (DNS, certs...) except this :
Creating a temporary folder to perform synchronization tests.
Failed to create temporary folder for performing tests.
Additional Details
Exception details:
Message: The response received from the service didn't contain valid XML.
Type: Microsoft.Exchange.WebServices.Data.ServiceRequestException
Stack trace:
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ReadXmlDeclaration(EwsServiceXmlReader reader)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ReadResponse(EwsServiceXmlReader ewsXmlReader, WebHeaderCollection responseHeaders)
at Microsoft.Exchange.WebServices.Data.SimpleServiceRequestBase.ReadResponse(IEwsHttpWebResponse response)
at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder(FolderId folderId, PropertySet propertySet)
at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder[TFolder](FolderId folderId, PropertySet propertySet)
at Microsoft.Exchange.Tools.ExRca.Tests.GetOrCreateSyncFolderTest.PerformTestReally()
Exception details:
Message: The expected XML node type was XmlDeclaration, but the actual type is Element.
Type: Microsoft.Exchange.WebServices.Data.ServiceXmlDeserializationException
Stack trace:
at Microsoft.Exchange.WebServices.Data.EwsXmlReader.Read(XmlNodeType nodeType)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ReadXmlDeclaration(EwsServiceXmlReader reader)
Elapsed Time: 1165 ms.
Here the autodiscover's answer:
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.
Additional Details
Elapsed Time: 996 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://MYDOMAIN.net:443/Autodiscover/Autodiscover.xml for user test@MYDOMAIN.net.
The Autodiscover XML response was successfully retrieved.
Additional Details
Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/a ... chema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/a ... hema/2006a">
<User>
<DisplayName>Test TESTO</DisplayName>
<DeploymentId>82e6297e-5364-4c17-be82-ee00e8d756a7</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://mail.MYDOMAIN.net/ews/Exchange.asmx</ASUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<EwsUrl>https://mail.MYDOMAIN.net/ews/Exchange.asmx</EwsUrl>
</Protocol>
</Account>
</Response>
</Autodiscover>
HTTP Response Headers:
Connection: keep-alive
Vary: Accept-Encoding, User-Agent
Content-Length: 912
Content-Type: text/xml
Date: Thu, 23 May 2019 09:45:39 GMT
Server: nginx
Elapsed Time: 996 ms.
I've also entered the zmcontrol commands for the proxy in this article:
https://wiki.zimbra.com/wiki/Steps_to_f ... _webclient
Somebody ever managed to have the EWS protocol work in the 8.8.12 NE of Zimbra?
Thanks a lot for your help !!