Bug 288467

Summary: improve filtering process for notification
Product: [Applications] kmail2 Reporter: Daniel Moyne <daniel.moyne>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: jb
Priority: NOR    
Version: 1.99.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Daniel Moyne 2011-12-08 10:58:13 UTC 
Version:           1.99.0 (using KDE 4.7.3) 
OS:                Linux

In my case the action of some filters is to change the target folder of some messages which is one of the typical expected action of filtering ; when those messages are received I get a notification (as set in KDE settings) saying that the message is in the reception box though it is not there due to the filtering action ; each message should get its proper notification with final destination which might be the dustbin which might be multiple folders in case of copy ; to summerize to read a message the user has to know where it is ; we might add in the notification the name of the filter that made an action on the message

Reproducible: Always

Steps to Reproduce:
filter with "copy" or "move" actions

Actual Results:  
messages no more in reception folder

Expected Results:  
notifications more detailed as to final destination and filtering action on each received message ; we could extend such procedure to notifications associated to sent messages

OS: Linux (x86_64) release 3.0.0-14-generic
Compiler: gcc
Comment 1 Jean-Baptiste Mardelle 2012-01-07 12:57:01 UTC 
Issue still there on KDE 4.8 RC2, and I would rather mark it as a bug than a wishlist.
Using KMail 4.8 RC2 with an IMAP accout. The notification message is saying 

1 new message in Account/Folder

Most of the time, the message is moved to another folder by a filtering action and the notification messages says "new message in Inbox", but so there is nothing new in inbox which is confusing.

Sometimes, thought the notification displays the correct folder. So I guess there is some kind of race condition between the filter job and the notification job. Would be better to wait for all filtering jobs to be finished before triggering the notification.
Comment 2 Jonathan Marten 2012-01-26 15:30:08 UTC 

*** This bug has been marked as a duplicate of bug 118213 ***