-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm getting back nil for autodiscover #4
Comments
It's returning nil because nothing is resolving. I'm not hung up on this being the correct way to do it but that is the reason you are getting a nil result. |
I just pushed up a change to master that adds a simple logger. You can include it with |
It looks like it does resolve, it's just that the first attempt fails for certificate problems rather than the domain not responding (see http://is.gd/TxGOi1) |
My script is currently this:
and the output is
|
I've tried the same account on testconnectivity.microsoft.com, and I'm getting a positive result on https://autodiscover.han.nl:443/Autodiscover/Autodiscover.xml . |
Got it -- I passed the username as |
Yet on another system, I'm getting the old problem again (same script from above):
|
I've enabled debug logging on the embedded httpclient, this is what it shows: https://gist.github.com/eb32d9a02d297191118f55b870ede466 |
With this script:
I'm getting back
nil
for the autodiscover call. I have to do the ignore, as the certificate doesn't match the domain (the exchange admins say that there's no problem, but eM Client complains about this too).The text was updated successfully, but these errors were encountered: