Bug 323936 - The read/HAM/important flag will not be copied when flagging and copying is in the same filter rule
Summary: The read/HAM/important flag will not be copied when flagging and copying is i...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: 4.11
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-23 17:27 UTC by eric
Modified: 2017-01-07 21:33 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 eric 2013-08-23 17:27:15 UTC
I've made this filter rule:
Criteria:
    Match all messages
Actions:
    1) Mark As: Important (or read, or HAM)
    2) Copy Into Folder: Local Folders/Store
Advanced tab:
    If this filter matches, stop processing here
    Add this filter to the Apply Filter menu

Everything works as expected except that the copied e-mail is not marked as important, even though the e-mail was marked as important first before copied to the Store folder.

Reproducible: Always

Steps to Reproduce:
1. Make the rule described above
2. Select an e-mail and apply this rule

Actual Results:  
The original e-mail is marked as important (as expected);
There is a copied version of this e-mail is in the Store folder (as expected);
The copied version of this e-mail IS NOT marked as important.

Expected Results:  
The copied version of this e-mail is also marked as important because the original e-mail is marked important before it is copied to the Store folder.
Comment 1 Denis Kurz 2016-09-24 18:06:31 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 21:33:55 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.