Hello, Everyone
I am attempting to use KMail 4.9.2 on Fedora 17 to access my Gmail account. When I start KMail, the message view pane says this message:
"Retrieving Folder Contents
Please wait..."

And that's it. That message never goes away.

The actual emails in my Gmail account seem to be there (in KMail.) KMail is NOT unresponsive, but that message I quoted above never goes away. I try clicking on an email and nothing happens. I try clicking on another email, same result. The GUI remains responsive, other than the fact that I can't ready any email...

I know this is not much information, so feel free to ask me for whatever additional info that you may need.

Steven P. Ulrick

Assuming you are using IMAP (from the appearance of your message), does your account show as ready in the Setup? Are the ports configured?

Unhinged wrote:Assuming you are using IMAP (from the appearance of your message), does your account show as ready in the Setup? Are the ports configured?

Yes. At "Settings | Configure KMail | Accounts | Receiving" the incoming account named "Google Mail (meow8282)" has a little green icon next to the message "Ready"

"Settings | Configure KMail | Accounts | Receiving | Modify | Advanced | Connection Settings" has "993" as the port.

OK, now I'm getting annoyed... While I was typing all of the above, I JUST happened to notice that there was an email open in the Message View pane... So, for whatever reason it is now working.

Since I do have KMail set to index all of my emails, is it possible that that was what was causing my original problem? For what it's worth, if that WAS the problem, KMail gave me no indication whatsoever that that was what was holding things up.

Anyway, I'm glad it works now Thank you for your time.

Steven P. Ulrick

It seems that there is still more to this story. I am on 4.9.2, as well. It is routine that I am met with "Retrieving Folder Contents Please Wait...." messages. The folder that is being accessed is local. I am also on pop. I have a bad feeling that my emails will be lost again. Any suggestions about what to do?

It seems, at least for me, that this problem is resolved by kde4.9.4. It was related to high cpu utilization by kactivitymanager. I don't understand what exposed the bug now, but it is very nice that the issue is fixed.