Bug 343474 - password popup after failed contact, no more checks will be attemted
Summary: password popup after failed contact, no more checks will be attemted
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.14.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-28 18:30 UTC by Roger Larsson
Modified: 2018-01-31 16:50 UTC (History)
0 users

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 Roger Larsson 2015-01-28 18:30:09 UTC
Whenever kmail fails to retrieve a mail it expects that you got the wrong password and popsup a window for you to enter the "correct" one.

In my experience wrong password is the most unlikely reason...

There are also several design desicions in this that makes it difficult for end users (like my mother or my wife. YES happened to both of them...)
- popup might be hidden, user press check mail, nothing happens - at least it should move on top.
- there are some risk that a completely unrelated password gets entered (or some other random text)

A popup is fine but
- show status bar in kmail
- retry login at all checks
- let the popup contain other possible reasons for failure (DNS, server down - ping), let password be a non changeable field unless you click "Password changed on server but I forgot to change it here"...

Reproducible: Always

Steps to Reproduce:
1. Check mail (manually or wait for automatic) [server answer could not login, busy?] -> popup
2. send a mail to one of the checked accounts
3. Check mail (manually or wait for automatic) -> no mail arrives
4. Close popup
5. Check mail -> mail arrives

Actual Results:  
3. No mail is received

Expected Results:  
1. The popup is fine (but the password could be a bit more protected from accidental overwriting)
3. Retries with the given password, mail is received
Comment 1 Denis Kurz 2017-06-23 19:58:52 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:50:22 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.