Bug 338751 - filter agent ignore incoming emails when not in inbox
Summary: filter agent ignore incoming emails when not in inbox
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Mail Filter Agent (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-02 15:35 UTC by Ondrej Holecek
Modified: 2018-02-01 09:46 UTC (History)
2 users (show)

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 Ondrej Holecek 2014-09-02 15:35:02 UTC
In my IMAP account, I have two subdirectories in Inbox folder. I have a server side filters which filters some emails to these directories.
On my machine I have another set of filters which then should move these emails to local directories and remove from server.
This however does not work and since filter log remain empty I guess filter agent does not even try to filter emails outside of Inbox. In filter rules I have set to apply mentioned filters to incoming messages from all accounts.

Reproducible: Always

Steps to Reproduce:
1. create Inbox subfolders on IMAP server
2. let server filter to move some incoming messages to these directories
3. have local filter to match incoming messages

Actual Results:  
When message is not directly in Inbox it is not processed by filter agent

Expected Results:  
Filter agent should process incoming messages even when they are not in inbox
Comment 1 Ondrej Holecek 2014-09-02 15:37:48 UTC
Version is 4.14 (not available to select as of this writing)
Comment 2 piedro 2014-09-19 09:53:22 UTC
For me also the filter protocol log stays empty though I have set up spam filters. It worked for about half an hour and than stopped. So my guess is that the mail filter agent (though it shows as active in akonadi console) just somehow quits silently. This is worse than not working at all because the behaviour leads to some folders half filtered get refiltered on next start of KDE but some actions are omitted (cause nothing is "incoming" for example)... 

This is very annoying and seems to be a seious regression. 

piedro
Comment 3 Laurent Montel 2014-09-19 10:27:11 UTC
"This is very annoying and seems to be a seious regression. " it's not a regression. It was never implemented.
We look at mail from inbox not from all folders.
So indeed in a folder != inbox it will not work.
Comment 4 Ondrej Holecek 2014-09-19 14:20:30 UTC
(In reply to Laurent Montel from comment #3)
> We look at mail from inbox not from all folders.
> So indeed in a folder != inbox it will not work.

Just to be clear, does this basically mean WONTFIX?
At least option to specify incoming folder in filter will help.
Comment 5 Laurent Montel 2014-09-19 15:35:36 UTC
I didn't close it because I don't know if it's possible to implement filter on folder != inbox and how to do it.
So for the moment I don't close as wontfix
Comment 6 piedro 2014-09-19 16:27:25 UTC
Hi! 

Sry, I still do not understand: 

Filters  work on sent messages... even for IMAP folders... 
And I was under the impression that I can designate any IMAP folder to be the one used for sending. So "sent messages" is not an incoming folder but an arbitrary one. 
Still filtering there is possible... 

Also manual filtering is, or least was, possible, in folders or an a selection of mails (not necessarily located in incoming)... 

Plz could you clarify how this works at the moment and whether this is how it is supposed to work? 

thx for your efforts, 
piedro
Comment 7 piedro 2014-09-19 16:34:49 UTC
please note: 

the ceasing mail filter agent that I've been referring to in comment #2 is definitely some other issue and has nothing to do with this thread here. I apologize for any confusion, I didn't realize these issues cannot be connected...  

I will look further and open another bug with a more acurate description, if the problem persists. 

sry, piedro
Comment 8 Denis Kurz 2017-06-23 20:05:38 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 9 Denis Kurz 2018-02-01 09:46:14 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.