-
-
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
Exchange build numbers 15.20.x.x unsupported #221
Comments
Do you know which Exchange version this is? According to https://technet.microsoft.com/en-gb/library/hh135098(v=exchg.150).aspx the latest build is at 15.1.x.x, so getting a build number of 15.20.x.x is somewhat surprising. |
Using exchange 365 Here is the full header from the response <s:Header><h:ServerVersionInfo MajorVersion="15" MinorVersion="20" MajorBuildNumber="13" MinorBuildNumber="11" Version="V2017_07_11" xmlns:h="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/></s:Header> |
Thanks. This looks like the first versions of an Exchange 2017 being rolled out. I'll see what I can come up with in the next days. You could try forcing the version to Exchange2016 as described in https://github.com/ecederstrand/exchangelib/blob/master/README.rst#setup-and-connecting but I'm not 100% sure it'll work. |
Thanks for that, hopefully i'll hit the pain before everyone else does. 15: {
0: 'Exchange2013', # Minor builds starting from 847 are Exchange2013_SP1, see api_version()
1: 'Exchange2016',
20: 'Exchange2016',
} It has not crashed as yet, so fingers cross. |
Ok, thanks! That's a very good data point. |
Google can't find any mention of an Exchange 2017 version coming up, and the build number returns not hits, either. Before I commit a fix, can you please test if this also works (canged "Exchange0216" to "Exchange2017")? 15: {
0: 'Exchange2013',
1: 'Exchange2016',
20: 'Exchange2017',
} |
I tried changing it to "Exchange2017" and got the following: Results I have therefore made the following changes and it seems to work for now... Code Results |
Thanks for the extra testing! I'll get the changes worked in and release a new version in the weekend. |
I just tested |
Little bit late but if anyone comes across this while Googling, Exchange version 15.20 is Office Exchange 365 Online/Outlook.com. There was never an 'Exchange 2017'; they went from Exchange 2016 to Exchange 2019. |
There seems to be a versioning error that is causing the code to crash.
Calling:
response
Error
The text was updated successfully, but these errors were encountered: