| Summary: | Disconnected IMAP stalls on large folders | ||
|---|---|---|---|
| Product: | [Applications] kmail | Reporter: | Simon Edwards <simon> |
| Component: | IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WAITINGFORINFO | ||
| Severity: | normal | CC: | bjoern, sheldonh |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
Confirmed. I've just set up an old IMAP account in kmail-1.9.6 (kde-3.5.6, qt-3.3.8). It contains these folders: Archive 2006-12 2006-05 2005-10 2005-03 Sent 2006-12 2005-10 KMail is stuck in what appears to be an infinite loop. The progress bar shows 25% most of the time. Every now and then it blips up to 95% for a split second as it moves on to the next folder. But it just cycles through them, never stopping. So it spends most of its time saying: 2006-12 Retrieving message list 2006-05 Retrieving message list 2005-10 Retrieving message list 2005-03 Retrieving message list Archive Retrieving message list 2006-12 Retrieving message list 2005-10 Retrieving message list Sent Retrieving message list I may have the order wrong. My tcpdump looks the same. I forgot to mention that I'm running into this on Gentoo Linux, kernel 2.6.20 with glibc-2.5 and gcc-4.1.2, which I imagine is quite a different environment from that of the original poster. Still an issue in recent kmail versions? |
Version: (using KDE KDE 3.5.5) Installed from: Ubuntu Packages OS: Linux When syncronising disconnected IMAP with the server, the whole process stalls. I've placed a wireshark trace of the conversion between kmail and the bincimap server here: http://www.simonzone.com/software/kmail_bincimap_stall_bug.txt Both sides of the conversion are in the same file, so it is a bit hard to see who is saying what, but if you look at line 8282: * 720 FETCH (FLAGS (\Seen95 LIST "" "kde-bugs" You can see that bincimap was busy with a long reply, but kmail jumps in and issues command 95 before bincimap is ready. After that the syncronisation between the two just falls apart. I think that the big delay that I saw was the two programs waiting for each other.