Closed Bug 576906 Opened 14 years ago Closed 13 years ago

Search using "body contains linux-arm-kernel" returns wrong mails(false positive in Body Search)

Categories

(Thunderbird :: Search, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: wedunn, Unassigned)

References

(Blocks 1 open bug)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 GTB7.1 ( .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.8pre) Gecko/20100704 Lightning/1.0b2 Lanikai/3.1.1pre (July 4, 2010)

Win-XP Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.8pre) Gecko/20100704 Lightning/1.0b2 Lanikai/3.1.1pre (July 4, 2010)

Search Messages using "Body Contains text" returns wrong messages.  I tried both a single search on Body Contains "linux-arm-kernel" and as a three-term search on "linux", "arm", and "kernel" using all terms required.  Many messages were returned that contain none of the search terms.  Not all messages containing the search terms were returned.

Reproducible: Always

Steps to Reproduce:
1.  Menu Edit/Find/Search Messages/
2.  Select "Body" in first box
3.  Select "Contains" in second box
4.  Enter "linux-arm-kernel" in third box or enter "linux", "arm", "kernel" on separate lines
5.  Make sure "Match all of the following" button is selected
6.  Click "Search" button
Actual Results:  
Message containing none of the search terms mixed with a few messages containing search terms.  No pattern evident.

Expected Results:  
Message containing search terms
Anything in Tools -> Error console ?

Have you tried safe mode? (see https://support.mozillamessaging.com/en-US/kb/Safe+Mode for more information)
Worse - the key 'body' is not always visible:

see: https://bugzilla.mozilla.org/show_bug.cgi?id=518188

This is with nightly 3.1.3pre build as of yesterday.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Duped bug by comment #3 seems "search of message/rfc822 part, then mime header line in message/rfc822 part matches" case, because that bug referes to phenomenon "Content-Disposition: attachment matches".
Re-opening.

There are two kinds of known issue of "header is searched".
(a) Tb searches "message body data of message/rfc822 part" == a mail data stream
(b) bug 697021 on multipart mail. (Tb searches message header of next mail)

To William E Dunn(bug opener):

Is any found mail by your search multipart mail?
If so, is there message/rfc822 part in found mails? 
Is there any mail which has "linux-arm-kernel" header at top part of message headers, in same mail folder?
If "Order Received" column is shown and mails are sorted by the column in ascending order, does mail next to a found mail contain "linux-arm-kernel" header?

If "search of message/rfc822 part" is not involved in your case, you may be looking phenomenon of bug 697021.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: DUPLICATE → ---
Bug for known issue of (a) in comment #4 is bug 700541.
Summary: Search using "body contains" does not work → Search using "body contains" returns wrong mails(false positive in Body Search)
linux-arm-kernel seems mailing list name.
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> Using linux-arm-kernel
> To post a message to all the list members, send email to linux-arm-kernel@lists.infradead.org.
Mail address like linux-arm-kernel@... can perhaps appear in message header of many mails, if you subscribe linux-arm-kernel mailing list.
Summary: Search using "body contains" returns wrong mails(false positive in Body Search) → Search using "body contains linux-arm-kernel" returns wrong mails(false positive in Body Search)
No response for more than 3 months from bug opener. Because many similar reports already exist. No need to keep open this bug any more.
Closing as INCOMPLETE.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.