Bug 301067 - Special Folders attributes can not be changed
Summary: Special Folders attributes can not be changed
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-02 17:43 UTC by both1970
Modified: 2017-01-07 22:27 UTC (History)
0 users

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 both1970 2012-06-02 17:43:12 UTC
By default the Local Folders resource contains: inbox, outbox, sent-mail, wastebin/trash, drafts and templates.

With an identity, you can associate different sent, drafts and templates folders and these will be indicated as such by icons in the folders list. However, the inbox, outbox and wastebin/trash folders can not be changed through Kmail.

I am using a Maildir resource in my home directory, so there is no reason to have a separate ~/.local/share/local-folders directory with the special folders, since each of these exists in my ~/mail directory already. Ideally, I would be able to reassign all my special folders (for example outbox could be set in the Sender resource) and completely remove the Local Folders resource.

Reproducible: Always

Steps to Reproduce:
1. Add a maildir resource to a basic Kmail config
Actual Results:  
The special folders attribute can't be applied to the appropriate directories in the Maildir and the Local Folders can't be removed.

Expected Results:  
Allow the special folders attribute to be assigned as desired.
Comment 1 Denis Kurz 2016-09-24 18:00:41 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 22:27:43 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.