Closed Bug 380604 Opened 18 years ago Closed 16 years ago

TB 2.0 search does not correctly perform exact match against X-Spam-Level header

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 184490

People

(Reporter: serafinguard-bugzilla, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 Build Identifier: version 2.0.0.0 (20070326) When trying to search for messages with SpamAssassin-added headers, TB 2.0's search should allow users to filter on exact value of the X-Spam-Level header. For example, you should be able to find any message that has a X-Spam-Level header with the exact value "****". This doesn't work. Instead it appears to use a "contains" (substring) match instead of the "is" match selected in the UI. Reproducible: Always Steps to Reproduce: Here's how I reproduce it: - Find or add a spam message to my inbox. - Verify it has a high SA spam score by viewing headers (for example, X-Spam-Level: **********). - Right-click on Inbox and choose "Search..." to bring up the search window. - Choose "Customize" from the headers dropdown menu. - Add "X-Spam-Level" as a new customized header. - Choose "is" from the contains / is / begins with / ends with menu. - Enter "***" into the value field. - Click Search. Actual Results: The above-selected spam email is returned as a match. If I understand the UI correctly, this shouldn't happen because the field values are not an exact match. Expected Results: The filter should not return any messages that don't have exactly "***" as the value of the X-Spam-Level header field. There is no workaround I can think of. I'm running against IMAP, in case that matters.
Bug #378080 seems to describe a similar user goal (filtering on Spam Assassin fields), but also doesn't show how you can filter on a specific header value.
Can't tell -- could be a dup of bug 379000 or bug 184490 if the X-Spam-Level filter is considered to be a "custom" header.
This looks like a dup of bug 184490 to me, especially since the reporter is using IMAP.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.