Folder not found

[Torsten Roloff]

I've been using DavMail with Thunderbird/Debian Linux for a couple of years with our Exchange 2003 Server.

Now we are updating to Exchange 2010 and I'm having trouble connecting to the new server.

I changed the settings according to your FAQ. Login seems to work, the logs show a lot of xml/wsdl output (the same as when I use the browser to log in to https://mail.company.com/ews/exchange.asm).

After this, a request to get the msgfolderroot(?) is sent three times:

Category:   httpclient.wire.content
Message:        >> "<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages">
<soap:Header></soap:Header>
<soap:Body>
    <m:GetFolder>
        <m:FolderShape>
            <t:BaseShape>IdOnly</t:BaseShape>
            <t:AdditionalProperties>
                <t:ExtendedFieldURI PropertyTag="0x6752" PropertyType="Integer"/>
                <t:ExtendedFieldURI PropertyTag="0x3603" PropertyType="Integer"/>
                <t:ExtendedFieldURI PropertyTag="0x6751" PropertyType="Integer"/>
                <t:ExtendedFieldURI PropertyTag="0x3008" PropertyType="SystemTime"/>
                <t:ExtendedFieldURI PropertyTag="0x360a" PropertyType="Boolean"/>
                <t:ExtendedFieldURI PropertyTag="0x3602" PropertyType="Integer"/>
                <t:ExtendedFieldURI PropertyTag="0x3613" PropertyType="String"/>
                <t:FieldURI FieldURI="folder:DisplayName"/>
                <t:ExtendedFieldURI PropertyTag="0x670a" PropertyType="SystemTime"/>
                <t:ExtendedFieldURI PropertyTag="0x10f3" PropertyType="String"/>
            </t:AdditionalProperties>
        </m:FolderShape>
        <m:FolderIds>
            <t:DistinguishedFolderId Id="msgfolderroot"/>
        </m:FolderIds>
    </m:GetFolder>
</soap:Body>
</soap:Envelope>"

This results in

Category:   davmail.exchange.ExchangeSession
Message:    Folder  not found
Location:   davmail.exchange.ews.EwsExchangeSession.buildSessionInfo(EwsExchangeSession.java:248)

and finally

Category:   davmail.exchange.ExchangeSession
Message:        EWS end point not available
Location:   davmail.exchange.ExchangeSession.<init>(ExchangeSession.java:238)

DavMail version is 4.5.1-2303.

Do you have any idea, what might cause the problem?

Thanks,
Torsten

[Torsten Roloff]

After looking into the davmail.log (not only the debug console), I found that the exchange server returns an 500 System.ServiceModel.ServiceActivationException. I'll try to have a look at the IIS logs and find out whats going wrong.

2014-10-24 10:53:25,282 DEBUG [ImapConnection-45126] httpclient.wire.content  - >> "<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages"><soap:Header></soap:Header><soap:Body><m:GetFolder><m:FolderShape><t:BaseShape>IdOnly</t:BaseShape><t:AdditionalProperties><t:ExtendedFieldURI PropertyTag="0x6752" PropertyType="Integer"/><t:ExtendedFieldURI PropertyTag="0x3603" PropertyType="Integer"/><t:ExtendedFieldURI PropertyTag="0x6751" PropertyType="Integer"/><t:ExtendedFieldURI PropertyTag="0x3008" PropertyType="SystemTime"/><t:ExtendedFieldURI PropertyTag="0x360a" PropertyType="Boolean"/><t:ExtendedFieldURI PropertyTag="0x3602" PropertyType="Integer"/><t:ExtendedFieldURI PropertyTag="0x3613" PropertyType="String"/><t:FieldURI FieldURI="folder:DisplayName"/><t:ExtendedFieldURI PropertyTag="0x670a" PropertyType="SystemTime"/><t:ExtendedFieldURI PropertyTag="0x10f3" PropertyType="String"/></t:AdditionalProperties></m:FolderShape><m:FolderIds><t:DistinguishedFolderId Id="msgfolderroot"/></m:FolderIds></m:GetFolder></soap:Body></soap:Envelope>"
2014-10-24 10:53:25,282 DEBUG [ImapConnection-45126] org.apache.commons.httpclient.methods.EntityEnclosingMethod  - Request body sent
2014-10-24 10:53:25,282 DEBUG [ImapConnection-45126] org.apache.commons.httpclient.HttpConnection  - enter HttpConnection.flushRequestOutputStream()
2014-10-24 10:53:25,282 DEBUG [ImapConnection-45126] org.apache.commons.httpclient.HttpMethodBase  - enter HttpMethodBase.readResponse(HttpState, HttpConnection)
2014-10-24 10:53:25,282 DEBUG [ImapConnection-45126] org.apache.commons.httpclient.HttpMethodBase  - enter HttpMethodBase.readStatusLine(HttpState, HttpConnection)
2014-10-24 10:53:25,282 DEBUG [ImapConnection-45126] org.apache.commons.httpclient.HttpConnection  - enter HttpConnection.readLine()
2014-10-24 10:53:25,282 DEBUG [ImapConnection-45126] org.apache.commons.httpclient.HttpParser  - enter HttpParser.readLine(InputStream, String)
2014-10-24 10:53:25,282 DEBUG [ImapConnection-45126] org.apache.commons.httpclient.HttpParser  - enter HttpParser.readRawLine()
2014-10-24 10:53:25,287 DEBUG [ImapConnection-45126] httpclient.wire.header  - << "HTTP/1.1 500 System.ServiceModel.ServiceActivationException[\r][\n]"
2014-10-24 10:53:25,288 DEBUG [ImapConnection-45126] httpclient.wire.header  - << "HTTP/1.1 500 System.ServiceModel.ServiceActivationException[\r][\n]"

[Mickael Guessant]

Definitely a server side issue

Maybe related to this:
http://blogs.msdn.com/b/dvespa/archive/2009/12/22/how-to-configure-a-http-endpoint-for-exchange-web-services-in-exchange-2010.aspx