https://bugs.kde.org/show_bug.cgi?id=472282
--- Comment #2 from Andreas Cord-Landwehr <cordlandw...@kde.org> --- After some more debug outputs, essentially uncommenting the GOT/SENT debug lines in getmetadatajob.cpp and increasing the debug level to debug for kimap, I am very sure that the Kolab server behaves in a way that some calls to "GETMETADATA (DEPTH infinity)" never are answered and thus the socket timeout is hit. What is quite interesting, in the same IMAP session the exact same call, eg C: A000008 GETMETADATA (DEPTH infinity) "KDE/Community" (/shared) S: * METADATA KDE/Community ( /shared/vendor/cmu/cyrus-imapd/server imapb036.mykolab.com ) S: A000008 OK Completed at one point succeeds and a few seconds later C: A000015 GETMETADATA (DEPTH infinity) "KDE/Community" (/shared) never is answered (I modified getmetadatajob such that timeout is set to infinity and now after waiting 15 minutes, I am very sure that the sever never will answer). @heinz, do you see the same behavior? With my limited IMAP knowledge, as far as I can see, here is not much that can be done on the client Akonadi side other than some crude hacks that retry the getmetadatajob once a socket timeout is reached instead of tearing down the full connection. -- You are receiving this mail because: You are watching all bug changes.
