Bug 319958

Summary: KMail2 looses messages/empty received message
Product: [Applications] kmail2 Reporter: Bernhard Jungk <fire>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: critical    
Priority: NOR    
Version: 4.10.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
URL: http://fire.coldbloodedice.de/upload/kmail2_lost_message.png
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Bernhard Jungk 2013-05-17 17:38:12 UTC 
Sometimes a message is just plain empty and lost! (See screenshot, there I tried to open the selected mail.)
In the screenshot I tried to open the message, however the corresponding message dialog shows up a completely empty mail. If I close kmail2, the message vanished and has left for heaven ...

I think this is connected to a change in my internet connection while kmail2/akonadi tries to download mails. I witnessed this behavior now twice and everytime I had a) either lost the wireless connection or b) I changed the connection settings to use some VPN.

Therefore this may be as well be not connected to kmail2 but to akonadi. I'm not sure.

Reproducible: Always

Steps to Reproduce:
1. Wait until kmail2/akonadi tries to fetch new mails
2. While fetching mails, disconnect your computer from the internet 
Actual Results:  
The message is displayed in the message list, however, the message itself is empty.

Expected Results:  
I want to read my Mails!

- I'm using POP3 to fetch mails
- I'm using the "Use pipelining for faster mail download" option.
- I did not check "Leave fetched messages on the server", therefore at least two messages are no lost forever for me :-(
Comment 1 Denis Kurz 2016-09-24 17:54:53 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:30:06 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.