I have a corrupt folder of sorts and dimap goes only as far as that, displays a message box that the folder doesn't exist on the server, then stops. The only way to make it check mail again is to close kmail, kill -9 the slave, reopen kmail. It of course freezes at the same place again. kmail: WARNING: slotGetUserRightsResult: Retrieving the Access Control List on folder newimap://user@host:143/INBOX/myfolder/ failed. The server returned: Mailbox does not exist kmail: No uidvalidity available for folder myfolder kio (KIOJob): error 63 Unable to open folder INBOX/myfolder. The server replied: Mailbox does not exist
On Tuesday 04 May 2004 03:05, George Staikos wrote: > I have a corrupt folder of sorts and dimap goes only as far as that, displays > a message box that the folder doesn't exist on the server, then stops. That doesn't sound like the current dimap error handling - it always offers Continue/Cancel. Which version of kmfoldercachedimap.cpp and imapaccountbase.cpp was that with? Can you try updating? > kmail: WARNING: slotGetUserRightsResult: Retrieving the Access Control List on > folder newimap://user host:143/INBOX/myfolder/ failed. The server returned: > Mailbox does not exist > kmail: No uidvalidity available for folder myfolder > kio (KIOJob): error 63 Unable to open folder INBOX/myfolder. The server > replied: Mailbox does not exist That's all fine (well except the fact that the server lists a folder that doesn't exist in the first place..)
On Tuesday 04 May 2004 06:55, David Faure wrote: > ------- Additional Comments From faure kde org 2004-05-04 12:55 ------- > > On Tuesday 04 May 2004 03:05, George Staikos wrote: > > I have a corrupt folder of sorts and dimap goes only as far as that, > > displays a message box that the folder doesn't exist on the server, then > > stops. > > That doesn't sound like the current dimap error handling - it always offers > Continue/Cancel. > Which version of kmfoldercachedimap.cpp and imapaccountbase.cpp was that > with? Can you try updating? Yes it gave continue/cancel, but it still froze. My code was from April 28 CVS. > > kmail: WARNING: slotGetUserRightsResult: Retrieving the Access Control > > List on folder newimap://user host:143/INBOX/myfolder/ failed. The server > > returned: Mailbox does not exist > > kmail: No uidvalidity available for folder myfolder > > kio (KIOJob): error 63 Unable to open folder INBOX/myfolder. The server > > replied: Mailbox does not exist > > That's all fine (well except the fact that the server lists a folder that > doesn't exist in the first place..) IMP handles it without problems. I used IMP to repair my mailbox. Basically it looked like this on the kolab server: INBOX/ broken_folder/ Ok_child/ Another_ok_child/ broken_folder was only "broken" in the sense that it had no contents, only subfolders. It's clearly possible to handle this situation since IMP does. It actually detects them as such and displays them differently.
On Tuesday 04 May 2004 19:34, George Staikos wrote: > INBOX/ > broken_folder/ > Ok_child/ > Another_ok_child/ > > broken_folder was only "broken" in the sense that it had no contents, only > subfolders. I have ~ 10 of those and they are handled just fine. I believe the problem is more specific than that.
On Tuesday 04 May 2004 13:37, David Faure wrote: > On Tuesday 04 May 2004 19:34, George Staikos wrote: > > INBOX/ > > broken_folder/ > > Ok_child/ > > Another_ok_child/ > > > > broken_folder was only "broken" in the sense that it had no contents, > > only subfolders. > > I have ~ 10 of those and they are handled just fine. I believe the problem > is more specific than that. Are there index files in the directory on the server?
No idea how to reproduce this bug, I have no such corrupt folders. In any case - can you reproduce it with the current CVS?
On June 17, 2004 14:17, David Faure wrote: > ------- Additional Comments From faure kde org 2004-06-17 20:17 ------- > No idea how to reproduce this bug, I have no such corrupt folders. > In any case - can you reproduce it with the current CVS? IIRC, with kolab, just create a folder and then erase the cyrus index files off the server or erase some message files manually. Then try to use that folder. It should be usable from Mozilla for instance, or IMP.
No point in keeping this around anymore - it's too out of date to be useful