FS#35764 - [evolution-ews] says password is alwasy wrong
Attached to Project:
Arch Linux
Opened by Peter Weber (hoschi) - Wednesday, 12 June 2013, 08:34 GMT
Last edited by Jan Alexander Steffens (heftig) - Wednesday, 03 July 2013, 12:18 GMT
Opened by Peter Weber (hoschi) - Wednesday, 12 June 2013, 08:34 GMT
Last edited by Jan Alexander Steffens (heftig) - Wednesday, 03 July 2013, 12:18 GMT
|
Details
Description:
Since an upgrade on the 3.8.3 series of evolution, evolution-ews and evolution-data-server the support for Exchange seems to be broken. Evolutions alwasy requests the password for the Exchange-Account and reports, that the entered password is wrong. I've downgraded all three packages and everything works again. Additional info: * package version(s): evolution-3.8.3, evolution-data-server-3.8.3, evolution-ews-3.8.3 * config and/or log files etc.: the server is Microsoft-Exchange 2010, I think at least SP2 Steps to reproduce: 1. Upgrade to latest versions from official repositories 2. Restart GNOME or at least all componentes of Evolution 3. Enter your correct password, as requests by the upcoming dialog from evolution |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Wednesday, 03 July 2013, 12:18 GMT
Reason for closing: Works for me
Wednesday, 03 July 2013, 12:18 GMT
Reason for closing: Works for me
I'm sitting behind the proxy of my company, configured in network-manager. Our MS-Exchange-Server is reachable from inside and outside of the network.
I figured out that a newly created user on my computer can access the server with evolution "3.8.3" and evolution-ews "3.8.3". This was possible because I didn't set up the proxy-configuration in network-manager for the new user.
Final solution:
1. I deleted all configuration files of evolution
rm -rf ~/.local/share/evolution
rm -rf ~/.gconf/apps/evolution
rm -rf ~/.cache/evolution
dconf reset -f /org/gnome/evolution/
2. Remove proxy-settings from network-manager
3. Set up account in evolution
4. Inside Evolution: Edit->Preference->Network: Select Direct Connection
5. Add proxy-setting in network-manager
Maybe caused by our network. Maybe caused by evolution-ews.I don't know.