Bug 132181

Summary: "Could Not Delete Resource" error after IMAP account checked with Mac Mail
Product: [Applications] kmail Reporter: Lincoln Peters <sampln>
Component: disconnected IMAPAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WAITINGFORINFO    
Severity: normal CC: bjoern, tmh
Priority: NOR    
Version: 1.9.3   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Lincoln Peters 2006-08-10 06:58:37 UTC
Version:           1.9.3 (using KDE 3.5.4, Debian Package 4:3.5.4-2 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.16.20lincoln

I have an IMAP server that I access in disconnected mode from my desktop (running KMail on Debian/unstable) and a laptop (a Macintosh, running MacOS X 10.4.7 and Mac Mail).  A few minutes after I check my e-mail using Mac Mail on the laptop (apparently the next time KMail checks for new mail), I always seem to get this error message from KMail:

Error while deleting messages on the server:

Could Not Delete Resource

An attempt to delete the specified resource
imap://lincoln@localhost:143/INBOX/;UID=0,0,0 failed

Details of the request:

* URL: (unknown)
* Date and time: Wednesday 09 August 2006 06:30 pm
* Additional information:
  imap://lincoln@Localhost:143/INBOX/;UID=0,0,0

Possible causes:

* Your access permissions may be inadequate to perform the
  requested operation on this resource.
* The specified resource may not exist.

Possible solutions:

* Check your access permissions on this resource
* Ensure that the resource exists, and try again.


The error message is annoying, but I can't find any signs of corruption in the IMAP account.

It could conceivably be a bug in my IMAP server (Dobecot 1.0rc2), but I can't be sure, and I imagine KMail should be able to work with broken IMAP servers when realistically possible.
Comment 1 Thomas McGuire 2007-05-24 17:16:38 UTC
*** Bug 145889 has been marked as a duplicate of this bug. ***
Comment 2 Thomas McGuire 2007-05-24 17:18:17 UTC
This could be related to bug 63353.
Comment 3 Björn Ruberg 2009-12-29 21:41:40 UTC
Is this still a problem in KDE 4.3?