Open Bug 600928 Opened 14 years ago Updated 2 years ago

Quick Filter by Sender should include "reply-to" header matches

Categories

(Thunderbird :: Search, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: eric, Unassigned)

References

(Depends on 1 open bug, Blocks 2 open bugs)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 Build Identifier: Message filter by Sender should include "reply-to". Reproducible: Always
you mean in the facetted serch (the very html one) ?
I'm not sure what you mean, but it's the filter messages feature, from the "Filter these messages... <Ctrl+F>" textbox.
Summary: Filter by sender should include "reply-to". → Filter by sender should include "reply-to" in quick-search
Quick Filter (per the UI)
Summary: Filter by sender should include "reply-to" in quick-search → Filter by sender should include "reply-to" in quick-search / Quick Filter
We have the same RFE for "All Adresses" (Bug 535879) -> confirming. This RFE has an UX perspective focused on Quick Filter Bar. It's not about message filters or Search messages dialogue (yet). I suppose it's better to handle those separately, if technically possible. We should discuss how this can be realized technically in terms of nsMsgSearchAttributes, and how this should reflect in message filters / Search messages filter options.
Blocks: 535879
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 7 → All
Hardware: x86 → All
Summary: Filter by sender should include "reply-to" in quick-search / Quick Filter → Quick Filter by Sender should include "reply-to" matches
Summary: Quick Filter by Sender should include "reply-to" matches → Quick Filter by Sender should include "reply-to" header matches
I understand that bug 212619 seeks to add the missing nsMsgSearchAttribute for "reply-to" (supported by Mike Cowperthwaite's Bug 212619 Comment 9), and hence is technical prerequisite of this bug.
Depends on: 212619
Blocks: 1127267
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.