Bug 279248

Summary: While filtering the message list always jumps back to the message selected before the filtering
Product: [Applications] kmail2 Reporter: S. Burmeister <sven.burmeister>
Component: message listAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: Craig.Magina, thomas
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description S. Burmeister 2011-08-03 04:07:19 UTC 
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

Kmail saves the message that was selected last per folder.

While it filters emails, e.g. from an imap account to local folders it updates the message view of all local folders every few seconds (maybe even after each message that was moved to some folder), even for those folders that did not get new messages. (bug 1)

Further, when updating the message list it always jumps back to the message that was selected the last time the user changed to another folder. This makes it impossible to read emails while filtering is going on.

Reproducible: Always

Steps to Reproduce:
Filter messages from an imap account to local folders.
While kmail filters select different message within a local folder.

Actual Results:  
Kmail jumps back to the message that was selected the last time before the folder was changed.

Expected Results:  
Do not update message lists of folders that did not get new emails.
Stick to the currently selected message.
Comment 1 Craig Magina 2011-08-30 13:13:50 UTC 
I can confirm this.  It makes reading e-mail very frustrating.
Comment 2 Thomas Tanghus 2011-09-01 09:03:35 UTC 
Related to Bug #279257 by original submitter.
Comment 3 Denis Kurz 2016-09-24 18:18:19 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 4 Denis Kurz 2017-01-07 22:36:43 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.