Bug 258403

Summary:	imap resource: gmail Unknown resource [Gmail]
Product:	kresources	Reporter:	Mark <markotahal>
Component:	imap	Assignee:	Till Adam <adam>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	ipstanistreet
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:

Description Mark 2010-11-30 17:36:31 UTC

Version:           unspecified (using KDE 4.5.80) 
OS:                Linux

with kde4.6beta1 and after migrating to kmail2, 
I get this error for IMAP resource set to gmail.com: 

a Gmail - AconadiTray window pops up:
"Select failed, server replied: A000040 NO Unknown Mailbox: ( now in authenticated state ) ( Failure ) [ Gmail  ]"

I'm getting this message every time I try to sync gmail, the number A??? changes by time. Although this happens, my other gmail folders (Inbox and other labels) synchronize well. 

The [Gmail] folder is created automatically by kmail (I don't see it in gmail web interface) and contains subfolders: Sent, Smap, Starred, All. 

Can anyone confirm? I had some troubles migrating and my new kmail seems buggy. 

(I chose the Delete local folders option at migration)

Reproducible: Always

Steps to Reproduce:
sync your gmail account in kmail2

Comment 1 Ian Stanistreet 2010-12-01 05:42:03 UTC

I had the same problem with one of my gmail accounts (my other had no problems). I removed and recreated the akonadi IMAP resource, but still saw the message every few minutes until I restarted akonaditray. It has worked as expected since then.
I too had trouble migrating to akonadi, and that's when the message first appeared. Meanwhile the migrator waited indefinately for some background process (sorry I can't be more precise, thats all it said) until I terminated it. It seems to be a migration problem.

Comment 2 Mark 2011-01-26 12:43:26 UTC

The problem still persists for me in kde 4.5.95 , I tried deleting and setting up the imap resource again but it didn't help (migration went fine this time)

Comment 3 Mark 2011-06-26 11:24:36 UTC


*** This bug has been marked as a duplicate of bug 258635 ***