Re: [Evolution] Failed logon due to server problem reports a password error

[Milan Crha <mcrha redhat com>]

On Sun, 2014-02-09 at 13:28 +0100, Johannes wrote:
> it seems the evolution-mapi reports a failed password when in fact the
> server is not available. There is an importand difference between the
> two. When a key ring stored password might still be correct it shouldn't
> be asked again from the user. evolution-mapi should silently retry the
> logon without bothering the user. Unless of course the password *is*
> wrong. 

        Hi,
you are right, there is a big difference between a wrong password and an
unreachable server. Unfortunately, libmapi (provided by an OpenChange
project) doesn't propagate such errors from samba stack (the one which
actually returns proper error codes from the network communication),
which makes it basically impossible to get the difference. Newer
evolution-mapi (definitely in 3.10.x) tries to use GLib's
GNetworkMonitor to check whether the destination server is reachable,
thus workaround the issue.

Anyway, the evolution-mapi is currently in a maintenance mode, it is
left for Exchange 2003 servers, as a replacement of evolution-exchange.
If you connect to Exchange 2007 server, or any newer, then I suggest to
switch to evolution-ews (also because Exchange 2013 servers have
disabled MAPI by default - not with RPC-over-HTTP, but samba/OpenChange
cannot connect with it yet). evolution-ews is under active development,
and works better/quicker in many aspects, with compare to
evolution-mapi.
        Bye,
        Milan