Bug 181686

Summary:	wrong error msg "Could Not Determine Resource Status"
Product:	[Applications] kmail	Reporter:	Thorsten Staerk <dev>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	jtamate
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Thorsten Staerk 2009-01-23 20:58:28 UTC

Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Whenever I connect to my mailbox, I get the error message "Could Not Determine Resource Status" in a disturbing messagebox. I immediately get it when I click on "Check Mail". But when I click "Continue" or "Cancel", everything is fine.

Comment 1 Jaime Torres 2009-02-01 22:11:20 UTC

I see two problems here:

* First one, in kdelibs the 
method in global.cpp
KIO_EXPORT QByteArray KIO::rawErrorDetail(int errorCode, const QString &errorText, const KUrl *reqUrl /*= 0L*/, int /*method = -1*/ )
in the 
case  KIO::ERR_COULD_NOT_STAT:
does not uses the errorText that is used by the kioslave imap4.

* Second problem to solve, only when the first one is solved: why it works at the second attempt but not at first?

Comment 2 Thorsten Staerk 2009-02-02 05:13:08 UTC

The full error text is

Error while getting folder information.
Could Not Determine Resource Status
An attempt to determine information about the status of the resource Unable to get information about folder INBOX.customflags. The server replied: Mailbox does not exist, or must be subscribed to., such as the resource name, type, size, etc., was unsuccessful.
Technical reason: Could Not Stat Resource
Details of the request:
URL: (unknown)
Date and time: Monday 02 February 2009 05:17
Additional information: Unable to get information about folder INBOX.customflags. The server replied: Mailbox does not exist, or must be subscribed to.
Possible causes:
The specified resource may not have existed or may not be accessible.
A protocol error or incompatibility may have occurred.
Although unlikely, a hardware error may have occurred.
Possible solutions:
Retry the request and ensure your authentication details are entered correctly.
Contact your appropriate computer support system, whether the system administrator, or technical support group for further assistance.

And the folder inbox.customflags - whatever that is - is never read successfully. So there is no "second attempt" that works.

Comment 3 Laurent Montel 2015-04-12 10:19:37 UTC

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.