Bug 326793 - kmail-4.11.2 fails to save to "sent-mail" after resuming and sending draft message
Summary: kmail-4.11.2 fails to save to "sent-mail" after resuming and sending draft me...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.11.2
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL: https://bugs.gentoo.org/show_bug.cgi?...
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-28 16:56 UTC by Zoltan Puskas
Modified: 2017-01-07 22:49 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 Zoltan Puskas 2013-10-28 16:56:58 UTC
Kmail is used with a Dovecot IMAP server. All folders are stored on IMAP (drafts, sent-mail, etc).
After a message is recalled from drafts and sent the message is saved in the wrong folder.
The message is saved to local sent-mail folder instead the one on the IMAP server. For every identity in the advanced tab the sent-mail folder is set to be on the IMAP. If message edited normally, without using the drafts folder, then mail is saved to correct sent-mail folder.

Reproducible: Always

Steps to Reproduce:
1. Edit new message.
2. Save to drafts.
3. Recall later from drafts (in my case I used two computers with identical setups, thus the reason for saving to drafts folder)
4. Edit (optional) and send mail
Actual Results:  
Message saved to local sent-mail folder.

Expected Results:  
Message saved to sent-mail folder on the IMAP server as per identity configuration.

Please see Gentoo bug report for more details.
Comment 1 Denis Kurz 2016-09-24 18:17:05 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:49:49 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.