Erik Cederstrand
Erik Cederstrand
Thanks for the update. I don't have any suggestions, unfortunately. I think your best bet is to work with your Exchange admin to work out where the remaining messages are...
Can you try out the referenced commit? I believe it may fix the error.
@rwludwig I just tested https://github.com/ecederstrand/exchangelib/commit/d9035d03960797f9277381845e4ec98f837798ea on an account with a public archive and it seems to fix the error. Can you try it out?
Changes are out in v5.3.0, BTW
Asuming this is fixed. Feel free to update here if not.
This is really weird. exchangelib is written in pure Python and supposedly entirely OS agnostic. To debug this, I would suggest that you [enable debug logging](https://ecederstrand.github.io/exchangelib/#troubleshooting) and compare the output...
@sch0lars Did you have a chance to revisit this?
Ok, so it's not about the Ubuntu version after all?
The best way to debug this is to follow the suggestion in https://github.com/ecederstrand/exchangelib/issues/1273#issuecomment-1964557146
Those two log lines can be ignored. You want to look for differences in the XML requests and responses.