Bug 281824

Summary:	kmail2 has problems with renaming folders
Product:	[Applications] kmail2	Reporter:	Johannes Hirte <johannes.hirte>
Component:	folders	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	null
Priority:	NOR
Version:	4.7
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Johannes Hirte 2011-09-11 19:48:08 UTC

Version:           4.7 (using KDE 4.7.1) 
OS:                Linux

I've created a new local folder with name "archiv" and appended accidently a +. So I renamed the folder (deleted the +). After this I moved some mail (121 messages) into this new, now renamed folder and got 121 error messages that the folder with name archiv+ could not be found.
I've tried to reproduce this with coping messages, but this didn't produced the error messages. A second try with moving gave me the errors again.
However, the message are moved to the correct place within kmail. I didn't checked in the filesystem.

Reproducible: Always

Steps to Reproduce:
create a new folder, rename it and move messages into it

Actual Results:  
for every message a error occours that the original created folder couldn't be found

Expected Results:  
messages should be moved without error

Comment 1 Johannes Hirte 2011-09-12 18:48:49 UTC

Ok, I have to correct this. The mails are now gone in kmail. I can see them in the filesystem in the original folder from where I moved them (inbox). But in kmail they're neither shown in the original folder nor the target folder.

Comment 2 Unknown 2013-01-23 09:58:25 UTC

Hello!

Is the problem still present after "logout" and "login" again?

Comment 3 Denis Kurz 2016-09-24 18:00:24 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 4 Denis Kurz 2017-01-07 21:32:54 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.