Bug 89457 - imap resource error when folders already exist
Summary: imap resource error when folders already exist
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Unmaintained
Component: IMAP (show other bugs)
Version: 1.7
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2004-09-14 02:28 UTC by Ben Damm
Modified: 2009-04-11 15:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Error message after attemping to create folders that already exist. (126.00 KB, image/jpeg)
2004-09-14 02:32 UTC, Ben Damm 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Damm 2004-09-14 02:28:56 UTC 
Version:           1.7 (using KDE 3.3.0,  (3.1))
Compiler:          gcc version 3.3.4 (Debian 1:3.3.4-9)
OS:                Linux (i686) release 2.6.7

After checking the "Enable IMAP resource functionality" checkbox in the Groupware tab of the Misc configuration group, KMail asks if I would like the folders created.

The problem is, the folders already exist in the IMAP account, which is connected to an Exchange 2000 server.  After the inevitable failure, an error is reported.  I shall screenshot the error and attach it.
Comment 1 Ben Damm 2004-09-14 02:32:12 UTC 
Created attachment 7518 [details]
Error message after attemping to create folders that already exist.

Note that in the moment before this errors appears, the icons for the
applicable folders flicker.
Comment 2 Till Adam 2005-01-23 12:24:56 UTC 
Did you select that exchange server's Inbox as the parent for the groupware folders?
Comment 3 Michael Leupold 2009-04-04 10:55:47 UTC 
I can't reproduce on trunk r948809 using Exchange 2003. KMail properly detects that there already are groupware folders with the required names.
Comment 4 Dominik Tritscher 2009-04-11 15:06:56 UTC 
Same here: Existing folders are detected correctly and used when setting up groupware functionality. I'm closing this bug.