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 575753 - When a POP3 server it's unavailabe evolution asks you again for a password
When a POP3 server it's unavailabe evolution asks you again for a password
Status: RESOLVED DUPLICATE of bug 571504
Product: evolution
Classification: Applications
Component: Mailer
2.22.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[pop] evolution[passwords]
Depends on:
Blocks:
 
 
Reported: 2009-03-17 20:53 UTC by Mateo Matachana López
Modified: 2009-07-31 19:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Mateo Matachana López 2009-03-17 20:53:36 UTC 
Please describe the problem:
When the POP3 server answers "-ERR [SYS/TEMP] Service Temporarily Unavailable", Evolution thinks you type a bad password and ask you again for a valid password. Also, when you try to retrieve all the mail, Evolution blocks waiting for an answer from the unavailable server.

Steps to reproduce:
1. Try to retrieve the mail from a temporarily unavailable pop3 server.
2. Type your password.
3. Wait some time, the password dialog will appear again asking you for a correct password.


Actual results:


Expected results:
A message telling you that "the server it's temporarily unavailable, please try again later.". Also, not try to receive email from a not available server.

Does this happen every time?


Other information:
Comment 1 Matthew Barnes 2009-03-17 21:52:42 UTC 
We've been fixing this kind of thing piecemeal for the various mail services.  Not sure if POP got fixed yet.  Can you please retry with Evolution 2.24.5 or later?
Comment 2 Mateo Matachana López 2009-03-17 23:15:59 UTC 
Tested with Evolution 2.24.5 and the same behaviour than in 2.22.3, it still fails.
Comment 3 André Klapper 2009-07-31 19:07:01 UTC 
Same issue as bug 571504.

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