Hi there, This is related to the thread "IMAP and permanent folder syncing" (https://marc.info/?t=144843807900004&r=1&w=2) which I'm not sure how to respond to as I'm not subscribed to the list. I'm using the the equivalent of disconnected IMAP which is meant to keep the messages locally. However, the messages keep refreshing again and again and there is also some random behavior. By refreshing, I mean that kmail/akonadi are actually re-downloading the whole folder again and again on random times. I.e they re-download all messages. This happens since the upgrade to this version. If I start akonadi from the command line I see its output, which indicates this. Here's an example: ------------------------------ log_imapresource: Starting retrieval for "23 - XXXXXXXXX" log_imapresource: Starting message retrieval. Elapsed(ms): 900 log_imapresource: MessageCount: 4442 Local message count: 4440 log_imapresource: UidNext: 258627 Local UidNext: 258626 log_imapresource: HighestModSeq: 0 Local HighestModSeq: 0 log_imapresource: Detected inconsistency in local cache, we're missing some messages. Server: 4442 Local: 4440 log_imapresource: Refetching complete mailbox. akonadiagentbase_log: 4442 4442 log_imapresource: Fetching 1 intervals Received: 10 In total: 10 Wanted: 4442 Received: 16 In total: 26 Wanted: 4442 Received: 2 In total: 28 Wanted: 4442 .... Received: 17 In total: 4436 Wanted: 4442 Received: 5 In total: 4441 Wanted: 4442 Received: 1 In total: 4442 Wanted: 4442 log_imapresource: Applying collection changes log_imapresource: Retrieval complete. Elapsed(ms): 65660 finished log_imapresource: "/23 - XXXXXX" ------------------------------ The above example is quite interesting as it is accompanied by another strangeness in kmail: The folder "23 - xxxx" (I'm masking the name here) is what is referenced in the logs. It is also the one I see in akonadiconsole being synced. However, after the retrieval, the messages are accounted in a completely different folder in kmail, which now has 4441 unread messages. Clicking on that folder I see one message (on a previous occurrence there were more). When clicking on the message I get blank contents and kmail writes this to the console: log_messagelist: View message selected [ "I'm masking the subject here" ] log_kmail: 103 "Unable to fetch item from backend (collection -1) : Unable to retrieve item from resource: Invalid item retrieved" At this point kmail did a timed synced (it's configured to check every ~5 minutes) and all the message from this folder were moved to the proper folder instead (i.e. it fixes itself). When that happened, the console displayed this: "Item query returned empty result set" My setup is debian test+experimental. akonadi-server 15.08.3, kmail 15.08.3, using akonadi's mysql. I have this behavior on two separate debian systems with similar setup but with different accounts. One is Gmail and the other is a company email server. I tried wiping the DIMAP account completely and recreating it from scratch (the messages above are from a kmail account that I created 2 weeks ago), but there was no luck. I have also tried "akonadictl fsck" and "akonadictl vacuum", but there wasn't any improvement. I just ran another "akonadictl fsck" and I got this: ... "Item \"1509180\" has no RID." "Item \"1509182\" has no RID." "Item \"1509183\" has no RID." "Item \"1509184\" has no RID." "Item \"1509185\" has no RID." "Found 64977 items without RID." "Found 0 dirty items." "Consistency check done." (lines above that scrolled outside of the scroll buffer, but there were no errors other than the RID one) Finally, the akonadi resource crashes with segmentation fault (sig 11) every now and then (e.g. it crashed right now). I don't think it correlates to the problem though. Is there anything more I could check to try and figure out what's wrong? Thanks, Stefanos Reproducible: Always
I'm experiencing this too. KMail relies on ``UIDNEXT'' to do incremental syncing. But some mail servers don't provide this. In such a case, KMail fails to sync incrementally and takes a long time fetching everything. The standard <https://tools.ietf.org/html/rfc3501> says: 'The STATUS command MUST NOT be used as a "check for new messages in the selected mailbox" operation' KMail needs other mechanisms of incremental syncing. It seems that few people are using KMail, and this bug won't get fixed soon.
Hi, I don't know if it's related, I'm experiencing some refresh IMAP Google sub folder. Kmail is stop to work and I've to restart akonadictl to find an issue. On Kmail interface is freezing on IMAP Google folder sync. If I put kwallet working with akonadi it's worse. I've an other IMAP acount from an other provider than Google and it's working fine. There is sub folder on this last one. In hope to help Regards,
My version Application: kmail (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-23-generic x86_64 Distribution: Ubuntu 18.04 LTS
I too am seeing this on multiple machines. My main IMAP server is running Cyrus.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Closing this because I no longer use KDE's IMAP for large mailboxes and can't confirm whether it's still an issue.