BedroomLANTilde~A: Alexios' HomepageSearch |
![]() |
||
Them KMail ‘Can't Determine Resource Status’ BluesDo you use KDE's mail user agent KMail? Do you use it with IMAP? If you do, you may be aware of various error messages such as ‘Unable to stat resource’. For the benefit of people looking for a solution using search engines, the top few lines of the error message read something like this: Error while getting folder information. Could Not Determine Resource Status An attempt to determine information about the status of the resource INBOX.customflags, such as the resource name, type, size, etc., was unsuccessful. Technical reason: Could Not Stat Resoure
I, and everyone at my company using KMail on our Courier IMAP server, used to get this error message every time KMail checked for new mail. This was a mere annoyance for a while, but eventually it became to much and I set out to debug it. I looked for a solution online and didn't find one. Armed with my trusty On our mail server, SolutionsThere are a couple of solutions which work in different cases. Please bear in mind that I'm by no means an IMAP guru. These solutions are empirical, and I didn't check the RFCs for their validity. Feel free to tell me I'm a cretin and suggest a better solution! The obvious way out of this issue is to delete the Initially, I attempted a fix where I recreated Also, you can enable subscriptions on your IMAP account, and make sure the Good luck! |
|
|
|
Comments
Hello and thanks for your article. I've recently had the same problem after my ISP upgraded their IMAP server. It appears that just re-enabling "subscriptions" via KMail's right-click menu fixed the errors and got rid of these messages.
The error message can be quite confusing until you realise where the salient information is (the Technical Reason and Additional Information are important in this case).
The reason I wrote this is that a lot of people (like you) managed to fix one of the many issues covered by this group of error messages, but I couldn't find an easy solution for my own problem.
Thanks for the comment!