Bug 307991

Summary:	Kmail doesn't move message to trash
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Christian Engels <christian.engels>
Component:	IMAP resource	Assignee:	Christian Mollekopf <chrigi_1>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	cluebat, kdepim-bugs, mollekopf, montel, vkrause
Priority:	NOR
Version:	4.9
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Christian Engels 2012-10-06 21:45:08 UTC

I am running against UW-Imapd and sometimes I can't delete messages (move to trash). The messages first appear to vanish but when I refresh the folders I just get them back while the emails are also now in the trash. Both are on the Imap server.

Reproducible: Sometimes

Steps to Reproduce:
1. Try to delete message in inbox
2. Switch folder to something else
3. Switch back to inbox

Comment 1 Christian Engels 2012-10-06 21:46:43 UTC

Forgot to mention Imap version UW imapd 2004.357.
On my dovecot or google mail imap servers it never happened.

~/.xsessions-error gives me the error: "akonadi_imap_resource_1(24686)/libakonadi Akonadi::ResourceBase::itemRetrieved: Item does not provide part "RFC822""

Comment 2 Laurent Montel 2013-05-28 07:45:29 UTC

You trash is in imap server or local folder ?

Comment 3 Christian Engels 2013-05-28 09:04:45 UTC

Trash is on the imap server.

Comment 4 Laurent Montel 2013-05-28 12:01:02 UTC

Ok know bug.
We need to fix it.

Comment 5 Kevin Ottens 2013-11-16 07:28:46 UTC

The IMAP resource has a new maintainer, reassigning to him.

Comment 6 Christian Mollekopf 2013-11-28 11:21:53 UTC

Laurent, do you know whats causing this bug?

Comment 7 cluebat 2014-03-02 13:02:19 UTC

Same problem with Kmail 4.10.5 and now 4.12.1 with Dovecot as the server. I hit delete on a message and it disappears. A few seconds later it reappears as a ghost (faded out, unselectable) with a notification of it's arrival. My phone, a separate IMAP client, sees it still in the Inbox as a regular message, which I can delete normally. The ghost entry in Kmail disappears when deleting the message via phone's MUA.

Comment 8 Christian Engels 2014-03-02 14:55:18 UTC

(In reply to comment #7)
> Same problem with Kmail 4.10.5 and now 4.12.1 with Dovecot as the server. I
> hit delete on a message and it disappears. A few seconds later it reappears
> as a ghost (faded out, unselectable) with a notification of it's arrival. My
> phone, a separate IMAP client, sees it still in the Inbox as a regular
> message, which I can delete normally. The ghost entry in Kmail disappears
> when deleting the message via phone's MUA.

Which dovecot version do you have? I can confirm that on Version 2.1.7 (current debian stable) with kmail 4.12 the bug does not happen. At least not on my Configuration. So I am not sure if that is the same bug.

Comment 9 cluebat 2014-03-04 22:33:26 UTC

Dovecot 2.2.10 hosted on FreeBSD 8.4-RELEASE-p7 amd64.

In case it makes any difference, I setup my IMAP account twice. The first time around I made the mistake of enabling Server Side Subscriptions, thus hitting bug # 316153. I deleted the account from Kmail and recreated it without that option. Now I have the option to delete (whereas before it was inactive / greyed out) but it doesn't actually delete. Very shortly after recreating the account, I upgraded from 4.10 to 4.12. The behavior in respect to delete failing is unchanged. I notice one artifact of recreating the account is that it is now imap_resource_1 instead of imap_resource_0 in akonadi although I can find no remnants of imap_resouce_0 so I doubt a conflict exists.

Comment 10 Denis Kurz 2016-09-24 20:37:49 UTC

This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 11 Denis Kurz 2017-01-07 22:19:32 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.