I am using evolution-exchange to contact OWA. OWA/Exchange is holding an
address-book. If the address-book from OWA can not be reached there is a
general error message "can't contact ldap-server".
So evolution is not really trying to contact an ldap-server. Just the
error-message is wrong. It must be something like "can't contact (OWA)-Server"
instead of "can't contact ldap-server"
This can easily be reproduced. When evolution is asking for the password for
the OWA-address-book just use a wrong password. It can also be reproduced, when
composing a message, click on "To" to open the address-book dialog and remove
the Lan-cable.
Maybe i have found the reason.
I am using evolution-exchange to contact OWA. OWA/Exchange is holding an
address-book. If the address-book from OWA can not be reached there is a
general error message "can't contact ldap-server".
So evolution is not really trying to contact an ldap-server. Just the
error-message is wrong. It must be something like "can't contact (OWA)-Server"
instead of "can't contact ldap-server"
See also alpha-unix. de/~iceroot/ ubuntu/ evolution- wrong-message. png
http://
This can easily be reproduced. When evolution is asking for the password for
the OWA-address-book just use a wrong password. It can also be reproduced, when
composing a message, click on "To" to open the address-book dialog and remove
the Lan-cable.
Imo there should be two things:
1. dont use ldap in the error-message when the target is not ldap /bugzilla. gnome.org/ show_bug. cgi?id= 668837)
2. dont say "can't be reached" when the credentials are wrong (also see my bug
https:/