Bug 323582

Summary: emails are opened in reply mode
Product: [Applications] kmail2 Reporter: Christian Schulze <lynx>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: grave    
Priority: NOR    
Version: 4.11   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Christian Schulze 2013-08-16 08:29:40 UTC 
If I open any received email by double clicking it, the mail is presented in reply-mode.
This poses multiple problems:
1. I can not save any attachments
2. I can not close this window by hitting 'ESC'
3. When closing it by hitting 'x', I am asked wether to save as draft or discard the mail.
4. After discarding the 'draft', the receiving date of the according mail is changed to the current date and time on the imap server.

This makes kmail absolutely unusable!!!! It messes up the server side!!!!! Has noone ever tested this prior to release????

Reproducible: Always

Steps to Reproduce:
1. open a received email (with attachment)
2. try to close by hitting 'ESC' (will fail)
3. try to save an attachment by right clicking it (no option availabe, since in wrong mode)
4. close draft by clicking on 'x' (will ask for save or discard)
5. take a USABLE mail client and check the receiving date of the mail opened in 1. (will be set to the current date/time)
Actual Results:  
see above

Expected Results:  
Well, mails should not be opened in reply mode!!!

This, including other issues with akonadi on imaps, is the worst condition I've ever seen kmail in  after about 10 years of usage.
Comment 1 Denis Kurz 2016-09-24 18:20:06 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:05:59 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.