Version: 1.2 (using KDE 3.5.1, Gentoo) Compiler: gcc version 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8) OS: Linux (i686) release 2.6.15-gentoo-r1 This is the second instance I have seen this behavior. Using cachedimap, a folder will become "read-only" ("n messages, y unread. Folder is read-only." displayed in the status bar). This happens without any obvious reasons and without the folder really being read-only. In the previous case checking it with a webmail client cleared up the problem (I figured this out yesterday after months of head scratching). I will try to see if that resolves this one as well but in either case I should have filed a bug report earlier. Cheers, JPD
Thanks for reporting JPD. Could you give steps to reproduce this behaviour? You can appreciate that otherwise all one can do is shoot in the dark:)
I'm not the reporter, but I'm having the same problem. I run Kmail 1.9.1 (KDE 3.5.1, Debian Package 4:3.5.1-2 (testing/unstable)), from Kontact. I cannot always reproduce the problem, but I can tell you what happened before it appeared. The first two times I experienced it, I had accidentally opened another kmail instance and clicked "run anyway" at the warning that there was already one kmail instance running. It was like this: I log in, a kmail instance starts loading (no visual feedback yet). I launch kmail, get the warning, I "run anyway", and I have two kmail instances open - both with a mislabelled readonly folder. The last time, my xserver crashed while I was checking the mail. At log in, the inbox was 'readonly'. As a weird thing, even though the delete and move operations are grayed out from the menu, I can still move messages out of the readonly folder by dragging them into another and choosing 'move' in the drop menu. My xserver has crashed in other ocasions, and I think I've ran two kmails without this behavior appearing, so I cannot guarantee that this will reproduce the problem - it'll barely increase the likelyhood of its appearance. The only way I've seen to recover the read-write status is by deleting the folder from my hard disk (rm -rf). I also experience from time to time the "annoying thing #1" from this post, perhaps it is related: https://mail.kde.org/pipermail/kdepim-users/2006-January/006474.html Regards, Zarrabeitia. P.S: Wild guess - could it be that a lock didn't get cleared properly when the crash/simultaneous access ocurred? Could I check it/clear it manually?
Sorry for taking so long to get back to this. To answer Ismail, I do not know how to reproduce this behaviour so it is most certainly a shot in the dark. I can't deny that it is happening though and has happened to me twice (once on two different machines). And a big thanks to Luis as he has given perhaps ways of reproducing this. The only things I can add is that I haven't ever knowingly launched two concurrent versions of kmail. By knowingly I mean I haven't been asked to "run anyway" because another instance was running. The problems may have occured around xserver crashes though but I can't remember at the moment. Sorry for the lack of specific details but I have no idea how to reproduce this bug nor how to fix its symptoms of getting readonly folders. It is severly annoying. (no exchange servers in my mix, one is Postfix, the other is Exim) Cheers, JPD