Bug 296053 - new mail always put into "sent"-folder, even with "keep replies in folder"
Summary: new mail always put into "sent"-folder, even with "keep replies in folder"
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-15 10:38 UTC by Milian Wolff
Modified: 2017-01-07 21:51 UTC (History)
2 users (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 Milian Wolff 2012-03-15 10:38:39 UTC
When one enables the "keep replies in this folder" folder property, new emails are still put into the associated identity's sent-folder. As Till told me, in KMail1 one was able to not associate a sent-folder with an identity, something which is not possible anymore in KMail2 (you always have some kind of sent-folder).

Thus, new mail will always be put into the sent folder and never be kept in a special folder. Workaround are either special identity-overrides per folder or filters.

I'd propose to either favorize the "keep replies in this folder" such that new mails are also kept there, or alternatively add another property "keep new mails in this folder".
Comment 1 phanisvara das 2013-12-22 17:12:14 UTC
at the time this was written, the "keep in the same folder" option was working for me. now, shortly before the upgrade to 4.12, it stopped workingt and i experience the same problem the OP does...
Comment 2 Denis Kurz 2016-09-24 18:07:02 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 3 Denis Kurz 2017-01-07 21:51:10 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.