Quick Filter Toolbar is not parsing senders' or recipients' name
Categories
(Thunderbird :: Search, defect)
Tracking
(Not tracked)
People
(Reporter: pevr, Unassigned)
References
Details
Comment 1•8 years ago
|
||
Yes, it happens also in safe mode and no error output. Without looking at any code, I'd say the "foo <mail@bar.org>" foo part is just not used for filtering.
Comment 3•5 years ago
|
||
I am able to reproduce this problem, too. I believe the issue arises from people who have an email address without their real name in it.
Ideally, an email will have address like "Jane Doe" <jane.doe@foobar.com>, but sometimes it is just the email part (i.e., <jane.doe@foobar.com>). If I have Jane Doe in my address book, the UI will replace the email with the real name and just show "Jane Doe". However, the quick search bar will not show the result if I type in "Jane Doe" because it appears to be searching the original information rather than the translated information.
From a user's perspective, this is difficult to understand, since the name is right there in the UI, but the search does not appear to work. However, assuming that is the underlying algorithm, it is working as implemented. I suggest refactoring to do the search on the translated address rather than the raw address.
Updated•3 years ago
|
Comment 5•4 months ago
|
||
Perhaps duplicate of bug 460737
Comment 6•4 months ago
|
||
The issue described in comment 3 still exists. I created an address book entry for one of my e-mail addresses under the name "spain ireland". When I view the message Thunderbird shows "spain ireland" something@herbison.com, but searching or filtering for spain doesn't find the message.
Delete the entry in the address book and the "name" actually in the message is shown. (And that name was always filterable and searchable.)
Comment 3 says " I believe the issue arises from people who have an email address without their real name in it" but it's worse than that as the address book entry overrides any real (or fake) name in included in the message (at least for the cases I've tried).
Since comment 0 says the name is in their address book it does look like bug 460737, but the scope of the issue is wider than the subject of that bug report as the problem exists for both searching and filtering.
Description
•