Bug 320158 - kmail2 doesn't display all emails
Summary: kmail2 doesn't display all emails
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: UI (show other bugs)
Version: 4.10.3
Platform: Debian unstable Linux
: NOR grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-23 07:31 UTC by Michael Meskes
Modified: 2017-01-07 21:49 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 Michael Meskes 2013-05-23 07:31:05 UTC
kmail2 works correctly in the beginning but after a while it decides to not show all the emails in a folder. This happens for both, my impa folders and my local folders. akonadiconsole displays all the emails in the folder. After another while new emails coming in get displayed again, the old ones still get not displayed. However, they are counted in the tree view as new emails.

When stopping kontact, the UI disappears but not the process itself. Also I always see processes like this hanging around when this happens:

kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-michael/klauncherhX5683.slave-socket local:/tmp/ksocket-michael/kontactst6178.slave-socket


Reproducible: Always




I tried with all database connectors possible and also with a brand new empty config. Problem is always the same. Imap server is local on the same machine. I have to kill and restart kmail several times a day to somehow use it as it usually only takes a couple minutes for the proble to appear.
Comment 1 Volker Kuhlmann 2013-08-17 00:21:46 UTC
Having the same problem here:
openSUSE 12.3, 4.10.5
kmail's default "Local Mail" maildir resource doesn't show all mail it contains, and can't be made to do so. Restarting kmail doesn't fix the problem, neithe rdoes restarting akonadi.
"Updating" the "Local Mail" folder in or exxcluding all subfolders, does absolutely nothing.

qdbus org.freedesktop.Akonadi.Control /AgentManager org.freedesktop.Akonadi.AgentManager.agentInstanceSynchronize akonadi_maildir_resource_0
Causes a synchronisation, as shown in kmail lower right corner (click blue up-arrow), but the sync itself seems to be broken as it doesn't align aknoadi's/kmail's brains to on-disk reality.

This is both unusable and useless!
Comment 2 Volker Kuhlmann 2013-08-17 00:56:51 UTC
Well I found the problem.

I refuse to have my mail stored in the bowels of kmail and want to know exactly hwere it is, so I shifted the "Local Mail" maildir folder to ~/Mail/local/. In the interim, something, somewhere, created a ~/Mail/.local.directory/ maildir folder instead and started using that instead.

While the .XXX.directory symlink lafaffel is a good way to flag which subdirectories are part of the mail directory and which are not, in all other respects it's an abominable PITA!!!
Comment 3 Hugo Costelha 2013-09-11 11:40:18 UTC
I am also facing similar situation with my IMAP accounts (I do not use the local folders). While the Inbox of my accounts show all email, most of the time the other folders only show email that was sent/received since kmail was last open.

Restarting kmail or akonadi  does not seem to change nothing. If I go to akonadiconsole I can see that all email is there.

I do not know if it is related, but sometimes sent emails just disappear, that is, they are not stored anywhere after being sent (I have disconnected imap with "Keep replies in folders" enabled).

I am using Kubuntu 12.04 with kmail 4.11.1.

Any suggestion for something to try?
Comment 4 Denis Kurz 2016-09-24 18:01:34 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 5 Denis Kurz 2017-01-07 21:49:40 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.