Bug 320178

Summary:	kmail2 unable to move mails from inbox tofolder
Product:	[Applications] kmail2	Reporter:	Thomas Arend <thomas>
Component:	commands and actions	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	grave	CC:	montel, thomas
Priority:	NOR
Version:	4.10.3
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description Thomas Arend 2013-05-23 16:12:59 UTC

kmail2 does not move messages via "drag and drop" nor via "move to folder" into a other folder.

As far as I know there is no work around anymore. Well done.

BTW: These messages should have been moved by a filter. But the nasty filter bug is still there. Some message are moved some are not.

Comment 1 Thomas Arend 2013-05-23 16:15:45 UTC

Looks like that this is only true for messages marked as spam.

Comment 2 Thomas Arend 2013-05-23 16:19:31 UTC

Sorry, I have another comment.

After restarting kmail2 / kontact, the messages are gone. Seems to be a problem with the display of moved / deleted messages in the message view.

Comment 3 Thomas Arend 2013-07-03 18:20:59 UTC

Today spam messages (kmail2 Version 4.10.4) marked with "X-Spam-Flag: Yes" are not moved but copied to the destination folder.

I would appreciate less frequent changes and better testing. kmail2 is since month in an pre-ALPHA state. 

I wish I could get the old working horse kmail 1 back.

Comment 4 Laurent Montel 2013-07-04 10:32:24 UTC

"I would appreciate less frequent changes and better testing. kmail2 is since month in an pre-ALPHA state. "
=> as it's pre-alpha for you why do you use it .???????
Please go back to kmail 1 :) it's better for you and for me, not necessary to read this type of comment.
Regards

Comment 5 Denis Kurz 2016-09-24 18:17:32 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 6 Denis Kurz 2017-01-07 22:24:14 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.