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 587461 - Evolution does not accept valid password in POP account password dialog
Evolution does not accept valid password in POP account password dialog
Status: RESOLVED DUPLICATE of bug 603855
Product: evolution
Classification: Applications
Component: Mailer
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[passwords] evolution[pop]
Depends on:
Blocks:
 
 
Reported: 2009-06-30 19:50 UTC by José Alburquerque
Modified: 2014-02-23 15:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description José Alburquerque 2009-06-30 19:50:05 UTC
I'm running gnubiff and evolution on the same POOP account.  gnubiff periodically checks for new mail reporting the new mail that it finds.  Evolution also periodically checks for new mail, downloading it automatically.

Every so often, they both try to access the account at the same time in which case evolution pops up a dialog requesting the POP account password because it thinks that the password that it used is incorrect.

I always have the "Remember this password" option checked in the dialog (and also in the account preferences), but even if I enter the correct password, the pop up continues to appear requesting a password even if I enter the correct password.

What I'm requesting is that, if the pop up comes up, it should remember the password that was already valid and not ask for a new password.  In other words, maybe the pop up should come up with the most recently password on file.  If "OK" is pressed, it should try that password because it most probably is still valid and probably didn't work because of some account access clash.  Thanks.
Comment 1 André Klapper 2013-08-24 14:40:24 UTC
So if the server refuses the login (e.g. logged in too often in a timespan), this is what happens. This is definitely a duplicate of one of the "See Also" tickets.
Comment 2 André Klapper 2014-02-23 15:10:41 UTC

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