After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 584178 - "Password incorrect" error if server is down
"Password incorrect" error if server is down
Status: RESOLVED DUPLICATE of bug 337479
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.26.x
Other All
: Normal normal
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2009-05-29 03:33 UTC by D Haley
Modified: 2010-03-25 15:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description D Haley 2009-05-29 03:33:06 UTC
Please describe the problem:
Evolution claims that the password entered by the user is possibly incorrect, when the server is not responsive. Evolution should recognise and report the difference between password authentication failure, and failure to resolve server name/contact server.

Steps to reproduce:
1. disable your network card & remove stored passwords in evolution
2. Restart evolution
3. connect to your exchange account
4. Enter your password
5. Click on exclamation icon in status bar



Actual results:
User is prompted for password, even though the server is unavailable. Furthermore user recieves 

"Error while Opening folder exchange://USER@SERVER/personal/Inbox.

Could not authenticate to server. (Password incorrect?)"

Expected results:
User should not be asked for a password until server is verified to be contactable. User should then be asked for a password to authenticate. If the server is not contactable, user should be informed that the server is not available. If the server is available, user should be prompted for password and then told that authentication failed, if this is the case

Does this happen every time?
yes

Other information:
Comment 1 Milan Crha 2010-03-25 15:38:08 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 337479 ***