Closed Bug 378100 Opened 19 years ago Closed 19 years ago

search/message filter fails when subject has line wrap/carriage return

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 124641

People

(Reporter: mozkeith2, 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) I've received some emails where trying to filter based on the subject contents is failing. For instance, if I try to query for "Customer Milestones", it fails to find it, even though I can see it quite clearly in the subject line. Further examination shows that when the message was downloaded, the subject line was wrapped, like so (directly from the folder file on the OS): Subject: Status: Major ...[removed for privacy reasons]... Customer Milestones last week Nothing on the new line can be picked up in the search box, or a mail filter. It is not clear whether Thunderbird is inserting that line feed or not. I have some emails with longer subject lines that do NOT wrap, and only a few that do. Some (that wrap) were sent by Netscape 7.1, some by Thunderbird 1.5. In some cases, the very same message sent by TB 1.5 wrapped in one case, but did not wrap when a reply was sent (or vice versa). Reproducible: Sometimes Steps to Reproduce: 1. Send an email with a long subject line to yourself 2a. Fetch the message, then try to search for a word at the end of the subject line; OR 2b. Look at downloaded message contents to see if the subject wrapped (there's always a space on the next line, so you can regexp search ^Subject:.*\n<space>
DUP of Bug 338310 or Bug 124641 or Bug 184490? See mail source thru View/Message Source(CTRL+U), and check which case your problem is.
Marking as dupe of bug 124641.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Agreed. Sorry, I searched on TB as the product; didn't think to also search on Core.
You need to log in before you can comment on or make changes to this bug.