Bug 295098 - kmail does not fetch mails
Summary: kmail does not fetch mails
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.8
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-29 21:56 UTC by Christoph Bartoschek
Modified: 2017-01-07 22:32 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 Christoph Bartoschek 2012-02-29 21:56:11 UTC
Version:           4.8 (using KDE 4.8.0) 
OS:                Linux

I log in into my machine, start kmail and wait till new mails arrive. But kmail sometimes does not fetch any mail. The status indicator says that the services are preparing fetching mails.

I think this has something to do with the kwallet or ksecretsservice integration. Several times I have seen that kwalletmanager showed me my wallet empty. I then killed kwalletd and restarted akonadi. I was then asked for the password again and kmail started to work. Till now this always helped after I found this out.

I have the impression that kmail is extremely fragile when it comes to passwords. One should not enter a wrong password for the wallet. Needing two tries leads to trouble. I also see that already stored passwords are reasked.

Reproducible: Sometimes

Steps to Reproduce:
Try to enter a wrong password for your kwallet first. Or press ESC for the kwallet dialog.

Actual Results:  
Nothing is fetched. There is no network traffic from kmail or akonadi on port POP3 or POP3S

Expected Results:  
Mails are fetched.
Comment 1 Denis Kurz 2016-09-24 18:11:40 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:32:05 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.