Hello,

We finally got to move to KDE 4.13.3 on OS X/MacPorts, and I'm noticing a new issue with kmail. Even on Linux the marriage with a GMail imap account isn't the happiest because of a regular "too many simultaneous connections" problem. On Linux, I'd just cancel the attempt to let the account go offline, wait a bit, probably kill/restart the corresponding imap resource, and then do a check mail in kmail which will take the account back online.

When I do this under OS X, kmail remains stuck with the "retrieving email" screen, rather than showing me the message. It behaves as if the server doesn't reply, except that updates do seem to work without any errors being posted. Restarting just the imap resource is not enough, the only way to unblock this situation is to restart the akonadi server and all depending resources. Quite the overkill, and requiring a detour to akonadiconsole or a terminal.

Any idea what is causing this? It's likely to become a dealbreaker that would have me revert to KDE PIM 4.12.5 if not resolvable, because I fear the same thing will happen when I take kmail offline myself when moving to another machine.
(Which ought not be necessary in the first place, if akonadi_imap had better support management of the number of connections it leaves open...)

The actual message is of course "Retrieving folder", and the same blockage occurs also after having kept kmail offline for a certain time.

Do you know what kind of server are you trying to access?

Erm, yes - Google's gmail imap server, imap.gmail.com

Try to follow the steps outlined here: https://techbase.kde.org/Projects/PIM/A ... Debug_IMAP and see if anything useful comes up.

OK, scrap the idea that it's unique to 4.13.3 on OS X only. I updated my Kubuntu install to 4.14.1 from their backports ppa yesterday, and damn if I didn't have the exact same issue there too this morning. Generalised even, not limited to my gmail account but also the one on messagingengine.com .
In addition, there's always 1 agent that remains forever at 0% progress in kmail's activity indicator after restarting the akonadi server, either the mail dispatcher or the mail filter agent, requiring at least one more akonadi restart ...

There was also a very stubborn "too many simultaneous connections" error that remained even after I killed all possible clients on all online hosts here. I'm beginning to feel that akonadi_imap_resource should maybe have an option to close its connections after each check of a gmail account, except possibly for the one IDLE connection. That'd also make it a bit easier to predict at what interval it'd need to unlock a kwallet because right now that's impossible to tell (which leads to its own share of problems because kwalletd doesn't always post its windows up front, on Linux).

As you may know, there used to be a GMail resource for 4.14, however it's build-disabled because of many bugs that popped up prior to release.
In this case you may want to ask people like Dan and Christian directly to see how to debug your issue: best would be the #akonadi channel on Freenode.