[Akonadi] [Bug 472282] Kolab Now reports too many open connections

https://bugs.kde.org/show_bug.cgi?id=472282 Heinz Wiesinger changed: What|Removed |Added Resolution|FIXED |UPSTREAM --- Comment #5 from Heinz Wiesinger

[Akonadi] [Bug 472282] Kolab Now reports too many open connections

https://bugs.kde.org/show_bug.cgi?id=472282 Andreas Cord-Landwehr changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[Akonadi] [Bug 472282] Kolab Now reports too many open connections

https://bugs.kde.org/show_bug.cgi?id=472282 --- Comment #3 from Andreas Cord-Landwehr --- OK, I found a horrible workaround to not trigger this error: I did a local patch that filters the "METADATA" capability out of the announced IMAP server capabilities (before handing them over to KMail) and

[Akonadi] [Bug 472282] Kolab Now reports too many open connections

https://bugs.kde.org/show_bug.cgi?id=472282 --- Comment #2 from Andreas Cord-Landwehr --- 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

[Akonadi] [Bug 472282] Kolab Now reports too many open connections

https://bugs.kde.org/show_bug.cgi?id=472282 --- Comment #1 from Andreas Cord-Landwehr --- I had a slightly deeper look into this issue because I can also reproduce this behavior with the Kolabnow.com server: Using the KIMAP_LOGFILE logging option when restarting Akonadi I monitored the socket

[Akonadi] [Bug 472282] Kolab Now reports too many open connections

https://bugs.kde.org/show_bug.cgi?id=472282 Andreas Cord-Landwehr changed: What|Removed |Added CC||cordlandw...@kde.org -- You are