Bug 332197 - searching in specific/only-in folders still searches in all folders
Summary: searching in specific/only-in folders still searches in all folders
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.13 Pre
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-15 21:43 UTC by Martin Koller
Modified: 2017-01-07 22:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Koller 2014-03-15 21:43:15 UTC 
When I use the "Find Messages" dialog to search only in my sent-mail folder (maildir),
I get a search result which shows mails from completely different folders.

Reproducible: Always
Comment 1 Laurent Montel 2014-03-16 06:40:47 UTC 
Please update your kdepim.
It can't validate it.
Comment 2 Martin Koller 2014-03-16 10:12:45 UTC 
I don't understand your comment.
How current would you like to have my kdepim installation ?
It is 4.12.90-449.1 from openSuse 13.1, 
Build Time: Fr 14 Mär 2014 18:01:50 CET
Install Time:Fr 14 Mär 2014 22:04:42 CET
Comment 3 Martin Koller 2014-07-14 06:21:17 UTC 
I've now updated to "Platform Version 4.13.60", kmail "Version 4.15 pre"
and I still can reproduce the problem.
It does not happen with all folders, but e.g. always when I select the "inbox" or "sent mails" or "trash", but also other self-created folders, type "s" to open the find dialog, type "test" and start the search
Comment 4 Denis Kurz 2016-09-24 17:57:40 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 22:18:43 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.