| Summary: | Email retrieval logins are randomly unsuccessful | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Vladimir Stepanoff <v5234647> |
| Component: | commands and actions | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | nate, v5234647 |
| Priority: | NOR | ||
| Version: | 4.14.4 | ||
| Target Milestone: | --- | ||
| Platform: | Mageia RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | Screen print of error message | ||
That's a pretty old version of kmail. Can you reproduce the issue with something newer? (In reply to Nate Graham from comment #1) > That's a pretty old version of kmail. Can you reproduce the issue with > something newer? The current kmail version in Mageia 5 is 4.14.10 and it appears that the bug has almost disappeared compared to what was happening when I reported the bug. I had to switch to periodic manually controlled sessions. With this version stumbles are rare and kmail now runs continually, I have seen very few login problems over the last few months, often with Hotmail, that has known login delays. Mageia 5 is at end-of-life and a switch to Mageia 6 will probably upgrade kmail to an even newer version. I would say that from a user point of view, the bug has indeed disappeared. Great, thank you! |
Created attachment 103846 [details] Screen print of error message Using latest supported RPM Mageia kmail 4.14.5, which is not in your list. Kmail logins to mail servers are randomly unsuccessful (see attachment), but immediate manual retries with the pre-filled passwords are always successful. I.e. most of the time there is no problem with 5 minute intervals between email accesses. Several different POP3 mail servers with different email addresses are being used, including Hotmail. Kwallet is running and connected to kmail. Could this be a timeout situation where kmail is not waiting log enough for a response from kwallet/akonadi? I don't see any configuration options for such a timeout. Is there some logging that would indicate the problem?