![]() The same happens both on my personal computer and my work laptop (except on the laptop evolution 3.10 does not include the exchangecookie in its response).Īlso, at the same time evolution-ews stopped working (roughly mid-june 2017), the autodiscover service to get the OAB URL in the account configuration stopped working, again asking me for a password and treating me as if my password was wrong. Basically, everything looks as if my password was wrong. ![]() But then, after typing my password, I don't see any message sending the password (which might have been omitted from the log for security reasons) and it looks like the dialogue with the server goes back to square one: same negotiation to get an NTLM key and an exchangecookie while I get another password prompt in evolution. It provides me with both an "exchangecookie" and some NTLM key, after which evolution-ews responds using the same cookie and another NTLM key (which I assume is matched to the server's key) and shows me a password prompt. It seems that the exchange server responds normally at first. I disabled gnome-keyring to limit the investigation field but it does not seem to change anything. I have been studying the logs of evolution-ews (using the environment variable EWS_DEBUG=2), but I cannot see where it goes wrong. Have you by any chance figured out a solution to your problem? I am trying again now hoping that some update of evolution (or the server's configuration) might enable a solution but I am struggling. Since it happened at the same time for my personal computer (running Arch) and my work laptop (running an outdated evolution version on Ubuntu 14.04) I thought it was due to a change in the server's configuration (over which I have zero control and cannot even get information about from the IT services who do not care much about linux users). Except for me I have not been able to connect to the exchange server at all, as if my password was incorrect. I have been facing a similar issue since mid-june 2017 too. xinitrc contains as the arch wiki suggests:Įval $(/usr/bin/gnome-keyring-daemon -start -components=pkcs11,secrets,ssh) What would be a good starting point for debugging evolution and gnome-keyring?Įxtra/gnome-keyring 1:3.20.0+57+g9db67ef6-1 (gnome)ĭowngrading is not an option, since it breaks dependencies There are people reporting similar things out there, but not exactly the same.Īnybody here struggling with the same thing? I've tried installing seahorse and mess around there, resetting the passwords, rm the local password cache, nothing really seems to help. Needless to say, this is highly annoying. If I confirm all of them, evolution will not ask for a couple of minutes, then it starts all over again. Right after starting evolution I get about 10 times a password dialog, each of them prefilled with username and password. This only affects the exchange account ( evolution-ews ), other email accounts ( imap, pop ) work fine. As per an answer listed on How to access a Shared Mailbox using Thunderbird or other IMAP client you may just need to define, confirm, or change a unique alias for the shared mailbox in Exchange 2016 and then use the below syntax rather than what you tried per your question.For about two weeks, evolution keeps asking every few minutes for the password.
0 Comments
Leave a Reply. |