-
-
Notifications
You must be signed in to change notification settings - Fork 249
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
401 Unauthorized #28
Comments
Thanks for the kind words! This was answered in more depth in #16. In short, it's not possible to distinguish between a temporarily malfunctioning EWS service and incorrect credentials. If you do need immediate failures, version 1.7.0 introduced the |
Fantastic! That does the trick. Thanks a lot. |
|
|
First of all, this is an amazing library. Very thankful to all the authors.
So I have a Exchange 2013_SP1 server setup and I am testing failure cases. If I add a configuration with incorrect credentials. It goes in a loop and never returns (at least after 10mins). How do I restrict the number of retries before giving up, especially for the case for incorrect credentials.
The text was updated successfully, but these errors were encountered: