Hi,
I don't know, if I really do need to fill out a support request, or if it is a misconfiguration. We are using the following software to connect our linux users with exchange:
davmail.server=true
davmail.enableEws=true
davmail.url=https://host.domain.ch/ews/exchange.asmx
davmail.caldavPort=1080
davmail.imapPort=1143
davmail.ldapPort=1389
davmail.popPort=1110
davmail.smtpPort=1025
davmail.enableProxy=false
davmail.useSystemProxies=false
davmail.proxyHost=
davmail.proxyPort=
davmail.proxyUser=
davmail.proxyPassword=
davmail.noProxyFor=
davmail.allowRemote=true
davmail.bindAddress=xxx.xxx.xxx.xxx
davmail.clientSoTimeout=
davmail.ssl.keystoreType=
davmail.ssl.keystoreFile=
davmail.ssl.keystorePass=
davmail.ssl.keyPass=
davmail.server.certificate.hash=
davmail.ssl.nosecurecaldav=false
davmail.ssl.nosecureimap=false
davmail.ssl.nosecureldap=false
davmail.ssl.nosecurepop=false
davmail.ssl.nosecuresmtp=false
davmail.disableUpdateCheck=true
davmail.enableKeepalive=true
davmail.folderSizeLimit=0
davmail.defaultDomain=
davmail.caldavAlarmSound=
davmail.caldavPastDelay=90
davmail.forceActiveSyncUpdate=false
davmail.imapAutoExpunge=true
davmail.imapIdleDelay=
davmail.keepDelay=30
davmail.sentKeepDelay=90
davmail.popMarkReadOnRetr=false
davmail.smtpSaveInSent=false
davmail.logFilePath=/var/log/davmail.log
davmail.logFileSize=1MB
log4j.logger.davmail=ERROR
log4j.logger.httpclient.wire=ERROR
log4j.logger.org.apache.commons.httpclient=ERROR
log4j.rootLogger=ERROR
davmail.ssl.pkcs11Config=
davmail.ssl.pkcs11Library=
davmail.ssl.clientKeystoreType=
davmail.ssl.clientKeystoreFile=
davmail.ssl.clientKeystorePass=
davmail.disableGuiNotifications=true
davmail.showStartupBanner=false
davmail.enableKerberos=false
As you can see, I removed the domain name and the binding IP Adress in the above config sample.
The Problem is, that sometimes the synchronisation of public folders is very slow. Also, sometimes it does not work to synchronize a public folder at all. When I look at the logs, I see the following error message:
2015-03-20 13:44:35,931 ERROR [ImapConnection-59373] davmail.exchange.ExchangeSession - Ews endpoint not available at /ews/exchange.asmx status 500
2015-03-20 13:44:35,931 ERROR [ImapConnection-59373] davmail.exchange.ExchangeSession - EWS end point not available
2015-03-20 13:44:35,931 ERROR [ImapConnection-59373] davmail - EWS end point not available
davmail.exception.DavMailAuthenticationException: EWS end point not available
at davmail.exchange.ews.EwsExchangeSession.buildSessionInfo(EwsExchangeSession.java:259)
at davmail.exchange.ExchangeSession.<init>(ExchangeSession.java:235)
at davmail.exchange.ews.EwsExchangeSession.<init>(EwsExchangeSession.java:138)
at davmail.exchange.ExchangeSessionFactory.getInstance(ExchangeSessionFactory.java:143)
at davmail.exchange.ExchangeSessionFactory.getInstance(ExchangeSessionFactory.java:90)
at davmail.imap.ImapConnection.run(ImapConnection.java:112)
I'm having the impression, that this problem is the same as described in the following support request: http://sourceforge.net/p/davmail/support-requests/236/
Could you please have a look at it and maybe give me a hint, what I am doing wrong? Also, if there is anything to test, I will be happy to do it for you.
Best Regards
Mathias Vaterlaus
Have you tried downgrading to Java 1.7.0.72 ?
https://sourceforge.net/p/davmail/mailman/message/33587504/
thx for the tip. I now downgraded java to version 1.7.0.72. I will have a look, if it performs better than the newer version. I will report back as soon as possible.
I checked the log and the above error messages are back. So I guess, it has nothing to do with the newer java version. I updgraded java again, because the version 1.7.0.72 is only available via an overlay.
Last edit: Mathias Vaterlaus 2015-03-25
You should probably check Exchange logs on the server side: 500 means something is wrong on this side
Hi Mickael,
sorry, that I did not reply in such a long time. You were right, the problems come from the exchange server. It seems, that our ews users hit a throotling policy.
At the moment, I have configured davmail.folderSizeLimit=50 and everything works fine. But this introduces a regression, because only 50 elements are shown in the mailbox. Luckily, this does not apply to searches, so e-mails, which are not among the 50 newest are still displayed.
We now try to find the corresponding exchange policy and increase or disable it, so we can undo the foldersize change in davmail.
Again, thanks a lot for your help and tips.
Best regards
Mathias Vaterlaus