Bug 354875 - Kmail imap sync takes long time with FetchItems Error
Summary: Kmail imap sync takes long time with FetchItems Error
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-05 03:02 UTC by Sylvain
Modified: 2018-01-31 16:49 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 Sylvain 2015-11-05 03:02:47 UTC
perhaps a duplicate of https://bugs.kde.org/show_bug.cgi?id=338571 but the akonadi console do not match and the kmail version are different too.

Since upgrade to kmail 5.0 (now kmail 5.0.2) an imap folders takes forever to sync with lots of error in akonadi console. This only happen on one imap account (my university one, gmail and personal imap server syncs are working).

Reproducible: Always

Steps to Reproduce:
1.I don't know as it seems specific to one account on which I do not have control on.

Actual Results:  
The sync is extremely slow. i tried to remove old mails and now the mail count is 1862 but still it takes a very long time (>1h) to sync. Reset akonadi (delete folder, try with new user, etc.) did not do any good. Because the sync is slow, filtering the mails or even deleting some, result in duplicate and/or "ghost" greyed message. If I let the computer always on, it will finish to sync and remove the messages, most of the time.
Akonadi console output for the imap ressource spit the following error for what seems all messages:
[code]
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Command: "StreamPayload" Payload Name: "PLD:HEAD" Request: "0" Detination: "" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Command: "StreamPayload" Payload Name: "PLD:HEAD" Request: "1" Detination: "" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Command: "StreamPayload" Payload Name: "PLD:ENVELOPE" Request: "0" Detination: "" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Command: "StreamPayload" Payload Name: "PLD:ENVELOPE" Request: "1" Detination: "" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Command: "StreamPayload" Payload Name: "PLD:RFC822" Request: "0" Detination: "" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Command: "StreamPayload" Payload Name: "PLD:RFC822" Request: "1" Detination: "65489_r792" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Response: "FetchItems" Error Code: "0" Error Msg: "" ID: "29530" Revision: "0" Collection ID: "-1" Remote ID: "" Remote Revision: "" GID: "" Size: "0" Mimetype: "" Time: "QDateTime(2015-11-05 02:36:10.362 UTC Qt::TimeSpec(UTC))" Flags: "QVector()" Tags: { } Relations: { } Virtual References: "QVector()" Ancestors: { } Cached Parts: "QVector()" Parts: { } }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Response: "CreateItem" Error Code: "0" Error Msg: "" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1729 { Command: "CreateItem" Merge mode: "(Remote ID, Silent)" Collection: "UID 11" MimeType: "message/rfc822" GID: "" Remote ID: "4436" Remote Revision: "" Size: "273299" Time: "QDateTime( Qt::TimeSpec(LocalTime))" Tags: "Invalid scope" Added Tags: "Invalid scope" Removed Tags: "Invalid scope" Flags: "QSet()" Added Flags: "QSet(\SEEN, $ATTACHMENT)" Removed Flags: "QSet()" Attributes: { } Parts: "QSet(PLD:HEAD, PLD:ENVELOPE, PLD:RFC822)" }
[/code]

Expected Results:  
sync work as fast as in previous versions.

If you need more info tell me I will do my best to provide them.
Comment 1 Denis Kurz 2017-06-23 20:22:18 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.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 opportunity 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 2 Denis Kurz 2018-01-31 16:49:38 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.