Bug 350291 - Mail does not apear in sent
Summary: Mail does not apear in sent
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.14.2
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-16 13:29 UTC by Marcus Hardt
Modified: 2018-01-31 16:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Hardt 2015-07-16 13:29:46 UTC
Some mails I compose take longer, therefore I have several composers open. 

Now, Kmail and the akonadi processes like to be restarted every now and then ("kmail is offline" issue).

Nicely (thanks a LOT) the pre-composed mails stay intact and all composer windows are re-opened. However, these mails don't appear in the sent folder :(



Reproducible: Always

Steps to Reproduce:
1. Start kmail + compose some mail
2. Restart the stuff  my favourite on this is: akonadictl stop; sleep 7; for i in  kmail kdeinit4 klauncher kded4 kio_file kio_http_cache_cleaner akonadiserver; do pkill $i; done; ps aux | egrep "(akon|kde; kmail )"
3. Send the previously composed mail and a newly created one
4. Observe which one appears in the sent folder.

Actual Results:  
Pre composed one does not appear in sent

Expected Results:  
Pre composed one does appear in sent
Comment 1 Denis Kurz 2017-06-23 20:00:35 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:52:27 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.