Version: (using KDE KDE 3.3.0) Installed from: Debian testing/unstable Packages After a kde crash and kmail behaving weird (wanted to create imap folders that already exist) I just did File -> Rebuild local imap cache. A popup appeared telling me: "Error when displaying folder ;TYPE=LIST. You might have discovered a bug." I think so too, ";TYPE=LIST" looks like the part of an imap command to me. Another popup told me "Error when uploading folder xy. The folder xy could not be created on the server." The folder already exists on the server. I hit cancel and more of the ";TYPE=LIST" popups appeared. The only way to get the account working again was to delete and recreate it. (All text translated from german.)
Did you keep the kmailrc from when this happened? Otherwise, how can we reproduce this bug?
I didn't keep it. I think this behaviour was rather caused by the state of the crashed kmail cache than by any configuration setting. After recreating the account I'm using it with the same settings like before without any problems. Do you want the kmailrc anyway? I thought it might be some obvious bug in the imap code when a part of an imap command is parsed as a foldername. The server is courier 1.4.3 I'm gonna try to capture a dump of the imap connection when rebuilding the local cache in the next days.
> I didn't keep it. I think this behaviour was rather caused by the state of the crashed kmail cache than by any configuration setting. kmailrc "caches" much information about every folder, it's not only "user configuration". > After recreating the account I'm using it with the same settings like before without any problems. Do you want the kmailrc anyway? No, I wanted to see if the ";TYPE=LIST" appeared there when you got the problem. > I thought it might be some obvious bug in the imap code when a part of an imap command is parsed as a foldername. There's obviously a bug somewhere, the question is where :) > I'm gonna try to capture a dump of the imap connection when rebuilding the local cache in the next days. OK.
David (Foerster), any news on this?
I can reproduce this with the following way: Create a top-level directory (directly to the account), with the namespace of shared folders set to empty. Here's the debug output: kio_imap: IMAP4::listDir - imap://gyuri@localhost:143;TYPE=LIST kio_imap: imapParser::parseURL ;TYPE=LIST kio_imap: URL: box= ;TYPE=LIST, section= , type= , uid= , validity= , info= kio_imap: imapParse::namespaceForBox ;TYPE=LIST kio_imap: IMAP4::parseURL - namespace= kio_imap: IMAP4::parseURL - delimiter=. kio_imap: IMAP4::parseURL - box=;TYPE=LIST kio_imap: IMAP4::parseURL - return 3 kio_imap: IMAP4Protocol::listDir - listStr=;TYPE=LIST.% kio_imap: IMAP4Protocol::listDir - got 0 kio_imap: IMAP4Protocol::assureBox - opening box kio_imap: imapParser::sendCommand - setting current box to ;TYPE=LIST kio_imap: imapParser::parseResult - current box is now kio_imap: IMAP4::dispatch - command=80 kio_imap: IMAP4::dispatch - command=72 kio_imap: IMAP4::mkdir - imap://gyuri@localhost:143/kkk kio_imap: imapParser::parseURL /kkk kio_imap: URL: box= kkk, section= , type= , uid= , validity= , info= kio_imap: imapParse::namespaceForBox kkk kio_imap: IMAP4::parseURL - namespace= kio_imap: IMAP4::parseURL - delimiter=. kio_imap: IMAP4::parseURL - box=kkk kio_imap: IMAP4::parseURL - return 0 kio_imap: IMAP4::mkdir - create kkk kio_imap: IMAP4::mkdir - Permission denied
I can reproduce this in the following way: 1. Create a d-imap account, add the default groupware folders. 2. Now create a new folder 3. Try to sync - the error message will appear, the new folder not created on the server 4. Exit KMail, and launch again 5. Re-sync 6. The error message not appear, the new folder created on the server
Created attachment 12495 [details] Log where the error message appear (step 3 from my bug reproduction)
Created attachment 12496 [details] Log where the new folder created correctly (step 5 in my reproduction)
Some more info: After the creation of the new folder, ImapPath in kmailrc is empty. After I exit from KMail, the ImapPath written to kmailrc is good. So after restarting KMail, the folder creation succeeds.
Created attachment 16789 [details] Capture of the network traffic when the bug occurs It just happend to me again. (KMail from KDE 3.5.2). I captured the network traffic.
Created attachment 16790 [details] a part of my kmailrc This is a part of my kmailrc containing the account configuration. I don't feel like making the complete file available for public but will happily send it to any developer asking for it.
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.