Open Bug 315258 Opened 20 years ago Updated 3 years ago

Want "is/isn't in address book" option for custom headers

Categories

(MailNews Core :: Filters, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: mail, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5 Build Identifier: Thunderbird 1.5 (Windows/20051030) I wanted to make a message filter rule that uses one of my custom-added headers ('Sender') and one of my address books (the one I use as a white list of senders for spam-filtering purposes). When I choose my customized Sender header in the field in the first column of the Filter Rules dialogue Thunderbird does not give me the option to use 'is/isn't in my address book' in the operator (second) column. Please address. Reproducible: Always Steps to Reproduce:
I'm not sure if this is feasible without recognizing Sender (or Reply-To, Return-From, etc) as a standard, address-containing field; there are many "custom" headers that typically don't contain an address (Content-Type, Content-Transfer-Encoding, any number of X-Virus- or X-Spam-type headers), and it might be confusing to have those headers providing the same option. BTW, "is/isn't in my address book" isn't even implemented for To or CC -- that's bug 187768.
Summary: Should be able to use customized headers with white lists → Want "is/isn't in address book" option for custom headers
QA Contact: filters
Product: Core → MailNews Core
(In reply to comment #1) > BTW, "is/isn't in my address book" isn't even implemented for To or CC -- > that's bug 187768. Now it is. Validating the RFE.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: 474676
Shouldn;t this be a relatively easy fix? To allow that as a filter/search option? Its been here for 6 years now?
Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.
Severity: normal → S3
Duplicate of this bug: 1809837
See Also: → 187768
You need to log in before you can comment on or make changes to this bug.