GNOME Bugzilla – Bug 668837
evolution-exchange using OWA is asking for a password when the OWA-Server cant be reached
Last modified: 2013-07-23 14:30:08 UTC
i dont know if this is an evolution-exchange + OWA only issue or if it is a global evolution issue (with imap). When the network is down/OWA cant be reached, evolution-exchange is asking for the password instead of saying "server can not be reached". The next bad thing is i get two windows with a password-request, the mail-app and also the buildin calendar is asking for the password because the server cant be reached. also see https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/922580
I can confirm this bug, though I'm afraid no one will look at this, as evolution-exchange is mostly unmaintained these days.
*** Bug 679410 has been marked as a duplicate of this bug. ***
The "evolution-exchange" package only supports Exchange 2000 and 2003 servers. Newer versions such as Exchange 2007 and 2010 are not supported by "evolution-exchange". It is required to use the package "evolution-ews" (or to some extend "evolution-mapi") for newer version fo Exchange servers. If the problem/request described in this report still happens with a recent version of "evolution-ews" or "evolution-mapi", please add a comment to this report (and update the "product" setting accordingly if possible). There are currently no plans to continue the development of the package "evolution-exchange", so this report will soon be closed as WONTFIX. Thanks for your understanding and sorry that the reported problem was not solved in time in the package "evolution-exchange".
evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago. evolution-exchange is now deprecated and not under active development anymore. It is unlikely that there will be any further active development. Closing this report as WONTFIX as part of Bugzilla Housekeeping. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again. Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported. Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.