Bug 322871

Summary:	mail filters do not work for incoming messages if the destination folder of the pop3 resource is not the inbox
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Christian Trippe <christiandehne>
Component:	Mail Filter Agent	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	amantia
Priority:	NOR
Version:	4.11
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Christian Trippe 2013-07-27 07:54:35 UTC

A filter which is configured to only apply to a pop3-resource does not work when receiving the mail if the pop3 resource has a destination folder which is not the inbox (SpecialCollectionAttribute=inbox).

Manual applying the filter works.

It also works directly when receiving the message, if the filter is also applied to the local folder resource. 

Related and already marked as fixed bugs are:
bug 256389
bug 308008

Reproducible: Always

Steps to Reproduce:
1. Configure a filter to only apply for a pop3 resource which has a destination folder != inbox
2. Receive mails where the filter is expected to work, e.g. move it to another folder

Actual Results:  
mail is in the destination folder of the pop3 resource

Expected Results:  
filter should have worked and mail is in the destination folder of the filter

Comment 1 Graeme Hewson 2013-08-16 09:11:23 UTC

I'm unable to reproduce this. I set up a filter with "Subject contains foobar" and action "Move Into Folder akonadi-local/<folder>"; then in Advanced "from checked accounts only" and uncheck all but the one POP3 server. I also tried moving the test filter down the list, from first to second place.

I tried with two POP3 accounts, each with a different destination folder. Apart, obviously, from the account settings, there were other differences: one uses pipelining and the other doesn't; one uses encryption and the other doesn't. Everything worked for me.

Comment 2 András Manţia 2013-11-16 12:41:20 UTC

If you change the destination folder, the change is not noticed until you restart Akonadi, but once it is restarted, all works fine. I find this as a minor issue, I don't think POP3 destination mailbox is changed often.

Comment 3 Christian Trippe 2013-11-19 17:41:12 UTC

Hi Andras,

do I understand you correctly that this is supposed to work after an akonadi restart?

This bug is not about mails not beeing moved to the destination folder of a pop3 resource. This works fine. I did not even check if this only works after a restart of akoandi, but about mail filters not working in this setup. 

I can stll reproduce the following with KDE 4.11

Setup a pop3 resource with destinaton folder A (!=inbox) and A not beeing a subfolder of the inbox but on the same level, e.g. direct subfolder of the local folder.
Setup a filter to only apply to messages from this pop3-resource (this means do not apply it to the local folder resource). This filter should move the message to the folder B which is a subfolder of A.
Now receive a message which should be moved to folder B by the filter. However the message will end in folder A.

However I agree that this issue is miner.

Christian

Comment 4 András Manţia 2013-11-20 06:13:12 UTC

"do I understand you correctly that this is supposed to work after an akonadi restart?" Yes, that is what I see here. The filter agents doesn't detect changes in the POP3 configuration until it is restarted (which is usually done by a full akonadi restart).

Comment 5 Denis Kurz 2016-09-24 20:31:19 UTC

This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 6 Christian Trippe 2016-09-26 17:41:24 UTC

Works fine now with kmail/akonadi from KDE Applications 16.04.3.