Bug 306152 - Renaming folders meets with limited success
Summary: Renaming folders meets with limited success
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: 4.9.0
Platform: unspecified Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-02 04:55 UTC by Joe Biden
Modified: 2017-01-07 21:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Biden 2012-09-02 04:55:48 UTC
Folder structure:

Car
->MBOX-GoodInfo85

I believe the result of a conversion from kmail the old (and bug-free) to this kmail (I want to give up, but have 15+ years of email in)

So, I want to rename the folder, since I now have 100+ MBOX-prefaced folders, which mess up....everything, including my long-lost 400+ filters I set up over months.

Anyhow...I go into "Filder Properties", rename the folder...come back out. Same name. Go back into Folder Properties, the name is now changed, the name in the folder list magically changes. Exit, go back into program...no change.

Check on disk, and now I seem to have two structures: an mbox file, and a Maildir structure: the mbox seems to be the old mbox, the Maildir seems to be the converted maildir, and NOWHERE is the name I want it to be converted to.

This is quite some program we've got here. Nothing seems to work!

Reproducible: Always

Steps to Reproduce:
1.Rename folder
2. Check results
3.Profit!
Actual Results:  
Nothing is renamed

Expected Results:  
It to be renamed
Comment 1 Denis Kurz 2016-09-24 18:23:34 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 2 Denis Kurz 2017-01-07 21:33:33 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.