Summary: | Not all mails from a folder are shown in the message list | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | S. Burmeister <sven.burmeister> |
Component: | message list | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | aspotashev, cordlandwehr, jacob, krege, ryu, woebbeking |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | KMailConsole |
Description
S. Burmeister
2011-03-15 13:41:29 UTC
I've exactly the same problem ! My inbox view is empty whereas I've > 4000 messages. The counter is ok, but the view no... When the messages are freshly downloaded, they appear in the panel. But, as soon as I restart Kontact, they disapear ! The error is : kontact(3540)/libakonadi Akonadi::EntityTreeModelPrivate::fetchJobDone: Job error: "Erreur inconnue. (Unable to fetch item from backend)" > My inbox view is empty whereas I've > 4000 messages. The counter is ok, but the view no...
must be something else. I have no issue with 10k emails folders
(In reply to comment #3) > must be something else. I have no issue with 10k emails folders I agree with you. Size is not the problem. But my view is empty... Not only for the inbox folder but for others too. (Not all) (In reply to comment #4) > I agree with you. Size is not the problem. But my view is empty... Not only for > the inbox folder but for others too. (Not all) Then you might have hit bug 268040 hwich is a variant of this one. (In reply to comment #5) > Then you might have hit bug 268040 hwich is a variant of this one. Yep, it is the same for me. Folder is empty. It is a big inconvenient now. I have to check my mails with the webmail :'( Created attachment 58226 [details]
KMailConsole
Here is the full log after clicking on Inbox folder
Have the similar problem, pop3 connections. Mails are visible during one sessin after downloading them from server, but after kmailwas restarted they disappear from list, folder become empty. Looking at "~/.kde/.../mail/<My folder>/new" dir, they are exist on the hard drive, I could read them in any editor. There are some other folders in my tree, working fine. Reproduced: everytime. I have some filters moving messages from Inbox root to Inbox subfolders, and those folders can be viewed fine. My workaround was to remove the IMAP account from Akonadi and then re-add it. (In reply to comment #10) > My workaround was to remove the IMAP account from Akonadi and then re-add it. That seems to work. The question though is, what's different with the new account that makes it work. I have found out, that problem is in "Return-Path" field. In major part of folders downloaded letters start with "Return-Path" as a first string. In this folder letters placed without this field. I ran simple script added Return-Path (place there email from "From:" field) and it become work. Can't understand, why. The same letters, been moved to another folder, are visible without such modification. (In reply to comment #8) > Have the similar problem, pop3 connections. Mails are visible during one sessin > after downloading them from server, but after kmailwas restarted they disappear > from list, folder become empty. Looking at "~/.kde/.../mail/<My folder>/new" > dir, they are exist on the hard drive, I could read them in any editor. There > are some other folders in my tree, working fine. > > Reproduced: everytime. Btw. That's more bug 264127 than this one. Do you have enabled strifi by chance? For me that bug seems to happen more often if strigi is enabled. This bug is still present with kdepim 4.6 beta5... 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. 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. |