Comment 18 for bug 139433

Here is my scenario: I have two machines, both were running Edgy with kmail 1.9.6, and both were configured for groupware folders/imap resources. I have upgraded only one machine to Gutsy, now using kmail 1.9.6 (enterprise 0.20070907.709405). After the upgrade the Gutsy machine has the problem described in this bug.

One point of interest, before attempting the workaround here, I compared kmailrc on the Edgy machine and the Gutsy machine, and the [IMAP Resource] sections were exactly the same (except for the account ID's of course):

[IMAP Resource]
TheIMAPResourceEnabled=true
TheIMAPResourceFolderParent=.1869991014.directory/INBOX

In Edgy, the groupware folders still work fine, without a "TheIMAPResourceAccount=" line.

On the Gutsy machine I tried the workaround; manually adding the TheIMAPResourceAccount=<accountid>
After restarting kontact/kmail, I get the following prompt:
"KMail will now create the required groupware folders as subfolders of INBOX; if you do not want this, cancel and the IMAP resource will be disabled"

If I say yes/Continue, then the empty Contacts, Cal folders etc. show up in the [cached/disconnected] IMAP acct with the icons indicating they are associated with Contacts, etc. BUT when I try to sync the cached IMAP acct with the server, it fails (Error while uploading folder Could not make the folder **** on the server...) because the folders already exist on the server (and are full of data) so it cannot create them again, and so it will not sync the existing data either.

If I say Cancel to the "Kmail will now create the required groupware folders" prompt, then, as it promised, it disables the groupware functionality and unsets "TheIMAPResourceEnabled=true" in kmailrc. If I manually reset this value in kmailrc and restart kontact, it gives me the same "KMail will now create the required groupware folders...." prompt.

So the workaround does not work here.