Hi Milan, thanks for your response, its quite strange. Some requests work fine but a lot fail. I did enable the debug on evolution directly and there the behaviour is the same. If I click on a message, sometime it opens (see attached getitem_ok). Sometime it fails without doing anything else than clicking on the next message (see getitem_401). I suspect that it is caused by our load balancing of exchange. There seem to be multiple server. If I change the URL to access one of these servers directly, everything seems to work. While this workaround does work for me, it would be great to fix that scenario in Evolution (or the affected library). Who could be interested in chasing this issue? On 07/23/2018 01:33 PM, Milan Crha via evolution-list wrote:
On Sun, 2018-07-22 at 20:52 +0200, René Bühlmann via evolution-list wrote:Attached is the output of EWS_DEBUG=2 /usr/lib/evolution/evolution-source-registryHi, do not run debugging on the evolution-source-registry, run it on evolution itself instead. The evolution-source-registry is responsible to show you all configured books, calendars, memo lists and so on, but it doesn't do any mail operations. That's all done on the evolution side. Thus use this command instead: $ EWS_DEBUG=2 evolution &>log.txt By the way, your source registry log ended with 200, which means it was able to login to the server. It's expected that there are couple Unauhtorized responses, it's because libsoup (and evolution-ews) tries to connect without the user name (and "password") first, then the server tells it it requires credentials and evolution-ews asks for them afterwards. Bye, Milan _______________________________________________ evolution-list mailing list evolution-list gnome org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Attachment:
getitem_401
Description: Text document
Attachment:
getitem_ok
Description: Text document