Bug 348525 - new mail and some saved mail not listed in folders
Summary: new mail and some saved mail not listed in folders
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 4.14.1
Platform: Kubuntu Linux
: NOR grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-31 21:44 UTC by Alastair Preston
Modified: 2018-01-31 16:53 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 Alastair Preston 2015-05-31 21:44:55 UTC
For two days now kmail is failing to display message lists in several folders. When I click on get message kmail reports that it's downloading messages, but no message list appears in my inbox folder. There are also no messages showing in outbox and a few other folders where I have stored messages. Other folders seem to be ok - it is not all the folders that appear empty. 

I have reinstalled kmail, kontact, kio and several other related files to no avail.

Reproducible: Always

Steps to Reproduce:
1. Open kmail
2. click "check mail"
3.

Actual Results:  
New-message counter increments, but no messages appear in inbox.

Expected Results:  
messages should be listed inbox as they did until two days ago.

Kmail was working fine until 30 May 2015. I've made no changes to my hardware and made only regular Kubuntu updates. 
Email account is on a pop3 server.
No error messages appear when checking email.
Comment 1 Alastair Preston 2015-05-31 21:47:01 UTC
Sorry, that should read  "When I click on "check mail"....."
Comment 2 Denis Kurz 2017-06-23 19:58:37 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 3 Denis Kurz 2018-01-31 16:53:30 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.