Bug 344091 - Mail Filter on specific header, any header for a specific pop3 account fails matching
Summary: Mail Filter on specific header, any header for a specific pop3 account fails ...
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Mail Filter Agent (show other bugs)
Version: 5.2.3
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-12 19:36 UTC by Fab Stz
Modified: 2022-12-06 05:18 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 Fab Stz 2015-02-12 19:36:04 UTC
I filter an email based upon tag "X-Apparently-To" whose value is
X-Apparently-To: email@e.mail; Thu, 12 Feb 2015 19:09:14 +0000
email@e.mail is the mail to whom the message was addressed.
This email is received through a POP3 account.
The filter is applied on incoming emails, and it is precisely during reception that the filter doesn't match the rule.

Example of the filter :
[Filter #0]
Applicability=2
AutomaticName=false
ConfigureShortcut=false
ConfigureToolbar=false
Enabled=true
Icon=system-run
StopProcessingHere=true
ToolbarName=my_filter_name
accounts-set=akonadi_pop3_resource_5
actions=0
apply-on=check-mail,manual-filtering
contentsA=email@e.mail
fieldA=X-Apparently-To
funcA=contains
identifier=n91pLLiIzTY1p7Z4
name=my_filter_name
operator=or
rules=1


In additon, if I choose the filter <any header> / <message> it doesn't work either (filter log says it doesn't match)


However in any of these cases, filtering works :
- running the filters manually on the messages once it is in a folder
- filtering on the <recipients> or <To> works
- applying this filter rule to all incoming message of all accounts

NB : This is neither the same as bug 308008, nor as bug 322871 

Reproducible: Always




Debian jessie :
kdepimlibs : 4:4.14.2-2 --> 4.14.2
kdepim : 4:4.14.1-1 --> 4.14.1
Comment 1 Denis Kurz 2017-06-23 19:59:23 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 2 Fab Stz 2017-06-29 19:08:48 UTC
Not reproducible. Seems fixed in KMail 5.2.3
(versions shipped with debian jessie (stable) : kdepim 16.04.3)
Comment 3 Christophe Marin 2017-06-30 08:02:04 UTC
Thanks for the feedback
Comment 4 Fab Stz 2017-07-01 09:20:35 UTC
I reopen the bug because after updating my filtering rules I still have the problem...
I noticed that in the filtering log, it seems the value of the Field that I'm checking is not correctly detected, since there is no value for that field in the log:

When choosing to filter on the specific pop3 account the log says :
[11:08:21] 0 = "X-Apparently-To" <contains> "email@e.mail" ()

While when choosing to apply the filter to all accounts:
[11:11:20] 1 = "X-Apparently-To" <contains> "email@e.mail" (email@e.mail; Sat, 01 Jul 2017 08:50:47 +0000)
Comment 5 Justin Zobel 2022-11-06 09:25:17 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-11-21 05:12:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2022-12-06 05:18:41 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!