Bug 306033

Summary:	can not delete emails
Product:	[Applications] kmail2	Reporter:	Jim Ahderson <james>
Component:	folders	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel, slett
Priority:	NOR
Version:	4.8.2
Target Milestone:	---
Platform:	Mageia RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Jim Ahderson 2012-08-30 14:32:27 UTC

I moved emails into the trash folder, then emptied the trash.  When I went back to the original folder, the emails came back, one at a time.  Some times I get two copies of the returning emails.  A simple delete key would be nice?

Reproducible: Always

Steps to Reproduce:
1.move emails to trash
2.empty trash
3.return to original folder
Actual Results:  
emails reappear in original folder, one at a time.

Expected Results:  
deleted the emails

Comment 1 Laurent Montel 2012-08-30 15:26:45 UTC

Works fine here.
Imap ? pop3 ?
Verify your identity if there is not problem.

Trash is on imap ?etc.

Comment 2 slett 2014-09-05 14:14:51 UTC

I have recently (the last 2 days) experienced the same problem.  The account is IMAP, has been set up for quite a while with no problems.  Other email applications are able to delete/move mail, but kmail2 simply does not.  Even mail filters no longer work.


Would sending a filter log file help?

Comment 3 slett 2014-09-05 14:24:20 UTC

Here is an update.  For messages in local/trash, if I select "empty trash folder", I get the message "messages deleted successfully" in the status bar, but in fact the messages aren't deleted, but a new copy of all the messages appears in the trash folder, doubling the number of messages.

Comment 4 Denis Kurz 2016-09-24 18:07:10 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 5 Denis Kurz 2017-01-07 21:42:50 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.