Bug 329526 - password cleared if login refused by server
Summary: password cleared if login refused by server
Status: REPORTED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: POP3 Resource (show other bugs)
Version: 4.12
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-02 12:17 UTC by Christoph Thielecke
Modified: 2021-03-09 05:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Thielecke 2014-01-02 12:17:59 UTC
The password for an pop3 account is cleared when the server refused the account data. On next request cycle the user have to enter the password again. This behavior is problematic. There serveral providers which refuses the login when called to often within a time period or busy. Its very nasty for the user to enter the password alltimes again if the login has been failed before. I think the password dialog should be displayed to the user with prefilled password. Then  the user have the choice to enter a new password or simply hit enter to use the old password again. Addionally, it could be useful to have a check option in preferences of the pop3 ressource which allows to ignore login failitures and dont display the password dialog in that case.

Reproducible: Always

Steps to Reproduce:
1. create a pop3 ressource with account data from web.de (freemail), gmx (freemail) or t-online
2. request to pull mail fast manually (web.de: < 3min, gmx: < 30s, t-online: no time value known, randomly)
Actual Results:  
account data dialog displayed, username filled in, password removed

Expected Results:  
account data dialog displayed, username and password filled in
Comment 1 Justin Zobel 2021-03-09 05:46:36 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.