Bug 244930

Summary: kmail: Filtering on imap accounts is broken
Product: [Fedora] Fedora Reporter: Sebastian Vahl <fedora>
Component: kdepimAssignee: Than Ngo <than>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 7CC: gtwilliams, kevin, peter, rdieter, zeekec
Target Milestone: ---Keywords: Regression
Target Release: ---Flags: fedora: fedora_requires_release_note+
Hardware: All   
OS: Linux   
Fixed In Version: 3.5.7-10.svn20070926.ent.fc7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-24 07:03:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Sebastian Vahl 2007-06-19 21:32:40 UTC
Description of problem:
Automatically filtering on imap accounts mostly only works for the first mail. 
All mails after the first one would not be filtered. 
Manual filtering only works for 1-3 mails at once. All mails after them are 
crossed-out but not filtered.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Have multiple mails on an imap account
2. Try to apply filters manually to more than 3 mails


1. Have multiple mails on an imap account
2. Receive more than 1 mail on this account which would be filtered
Actual results:
Only the first mail would be filtered.

Expected results:
The filters would be applied to all mails

Additional info:
This seems to be a known upstream bug newly introduced in kdepim-3.5.7:

A reverted patch would maybe fix this: 

After a downgrade to kdepim-3.5.6 filtering works fine.

Comment 1 Kevin Kofler 2007-06-19 23:37:17 UTC
Unfortunately, reverting the patch might not be enough:

------- Additional Comment #24 From Alexey Morozov 2007-06-04 14:41 -------  
Just noticed: 
KMail with reverted r650963 applies filters to the new messages, except those 
which just arrived: that is if KMail receives a new message or messages they 
won't be processed during this transaction, only in the next check cycle. 
Does anybody actually understand how KMail filters are processed? 
------- Additional Comment #25 From Alexey Morozov 2007-06-05 07:24 -------  
I have to conclude: filter processing is seriously broken in KMail :-(. 
Now I have a simple filter (actually it's a default anti-spam filter which 
checks for X-Spam-Flag == YES and moves the message to trash). The header check 
simply doesn't work, although similar checks perfectly work in other 
filters :-( 
Could anybody explain how they are expected to work, step by step? 

Comment 2 Kevin Kofler 2007-07-13 06:47:04 UTC
Do we have any solution to this yet? We should really fix this regression 
sooner rather than later.

Comment 3 Rex Dieter 2007-07-20 12:21:39 UTC
It's pretty much out of our hands (waiting on upstream), unless somebody 'round
here turns into a kdepim dev/hacker.

Comment 4 Sebastian Vahl 2007-10-06 07:54:11 UTC
Uh. Just forgotten. kdepim-3.5.7-9.svn20070926.ent.fc8 (the enterprise branch) 
fixes the imap problem.

Comment 5 Garry T. Williams 2007-10-08 22:35:43 UTC
I can confirm the fix: kdepim-3.5.7-9.svn20070926.ent.fc8 restores IMAP inbox
filtering.  (I installed this on a F7 system from the fedora-development

Comment 6 Fedora Update System 2007-10-11 01:44:18 UTC
kdepim-3.5.7-10.svn20070926.ent.fc7 has been pushed to the Fedora 7 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update kdepim'

Comment 7 Sebastian Vahl 2007-10-11 20:37:53 UTC
Added "fedora_requires_release_note" "+"

We're using the more stable kdepim-enterprise for Fedora 8 (and also Fedora 7 
as an update).

Comment 8 Fedora Update System 2007-10-24 07:03:00 UTC
kdepim-3.5.7-10.svn20070926.ent.fc7 has been pushed to the Fedora 7 stable repository.  If problems still persist, please make note of it in this bug report.