Red Hat Bugzilla – Bug 972562
EWS support fails with horde server backend
Last modified: 2013-11-25 23:25:17 EST
Description of problem:
The current release of Horde contains EWS support - which I can confirm works just fine with the "Exchange" account option in the Win8 native Mail app
evolution-ews apparently insists on doing an autodiscover lookup - which is a bit broken I think with Horde. However, as I chose "custom", I think that means "manual" doesn't it?
Version-Release number of selected component (if applicable):
Try to set up an Exchange online account against a horde web server
Steps to Reproduce:
1. it just insists on doing the autodiscover - which will fail
Gives the following error
Failed to find ASUrl and OABUrl in autodiscover response
As I chose a "Custom", I think it should disable autodiscover and just go with the details I gave it.
Thanks for a bug report. You can check what autodiscover returned, if you run evolution from a console like this:
$ EWS_DEBUG=2 evolution
and then repeat the "Fetch URL" button click, but I'm afraid it'll just for a little debugging of Horde, rather than of debugging evolution-ews itself.
In any case, the "Fetch URL" click is not necessary, you can always file the URLs for the EWS protocol and if you know then also for the OAB yourself. It's true, there was a bug  with this non-clicking 'Fetch URL', but it is fixed since evolution-ews-3.7.92, thus 3.8.0 stable release.
As you have this filled against Fedora 19, I suppose you do have at least 3.8.0, right?
> As I chose a "Custom", I think it should disable autodiscover and just go
> with the details I gave it.
I'm sorry, but I do not know what you mean with the above. What 'custom' do you mean, please? The autodiscover process is not necessary, you can even keep the OAB URL empty, that is no problem. The autodiscover is there to make life easier for a user, to not dig for the exact URLs on their own, but it's not a mandatory step in any way. Maybe if you can explain more precisely what "fails with horde", what exactly you did, what evolution claims, then it'll be easier to help.
sorry, I never saw your followup until now.
I have since discovered horde doesn't support EWS - it only supports ActiveSync. So this is not going to work after all and it's not a bug with evolution