| Summary: | Mail Filter on specific header, any header for a specific pop3 account fails matching | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] Akonadi | Reporter: | Fab Stz <fabstz-it> |
| Component: | Mail Filter Agent | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 5.2.3 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Fab Stz
2015-02-12 19:36:04 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. Not reproducible. Seems fixed in KMail 5.2.3 (versions shipped with debian jessie (stable) : kdepim 16.04.3) Thanks for the feedback 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) 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! 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! 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! |