FindItem requests repeated forever. Nothing shows up in calendar.

[Gunnar Grim]

After setting up the Exchange calendar I get prompted for password. Then nothing appears to happen but the log quickly fills up with eternally repeated FindItem requests, see attached log.

[Simon Schubert (corecode)]

Can you try using the autodiscover?

[Gunnar Grim (gg-launchpad)]

Yes, I've tried that and it works but only when I am at the office and then only when I add the server name reported by autodiscover to my hosts file. I was hoping that I could use the host name that I use to access mail both from home and from the office.

[Simon Schubert (corecode)]

If your exchange admins do not allow access from outside, you're out of luck. you will need a vpn or you will have to convince your exchange admins to offer EWS for outside.

[Gunnar Grim (gg-launchpad)]

They do allow access from outside but not with autodiscover. I tested using wget to fetch the wsdl using the URL https://<mail-host>/EWS/Exchange.asmx and it works fine.

[Simon Schubert (corecode)]

What is the wsdl? What is important is that EWS actually works, and telling from your log it seems it doesn't.

[Gunnar Grim (gg-launchpad)]

The wsdl is the Web Service Definition Language file that describes which methods the EWS has. Connection and basic authorization works fine when I use wget to access the EWS.

[Simon Schubert (corecode)]

Yes, but which URL do you use? Which request? Can you send the FindRequest from the log manually? Can you check why autodiscover doesn't work?

[Gunnar Grim (gg-launchpad)]

I've now found out why autodiscover doesn't work from outside the office. The server name that autodiscover reports is not accessible from outside. With Outlook you need to configure an Exchange proxy server. I have tried setting it up as a general Thunderbird proxy but without success. Is it possible that your Exchange provider ignores the proxy settings?

[Simon Schubert (corecode)]

No idea. Also I don't think that the exchange proxy is the same as a http proxy. It looks like a misconfiguration on your Exchange server side. Maybe talk to the admins to see what's what.

[Gunnar Grim (gg-launchpad)]

I'm pretty sure the Exchange server is configured correctly. It "simply" requires that the client allows a http/https proxy to be configured, which is the case with Outlook. I'll do some verifications using wget or some coding and see if I can verify that this is in fact the problem.

[Simon Schubert (corecode)]

Did you ever fix this problem?