Multi-word message filters on HTML Body text may not work if lines are wrapped

RESOLVED EXPIRED

Status

RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: sbohdjal, Assigned: mscott)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Thunderbird version 1.0 (20041206)

If you set up a multi-word message filter (e.g., "Mozilla Thunderbird") for
"Body" text with the "Contains" option, the filter won't find a match if the
e-mail body is HTML formatted and the words happen to have a line break between
them ("\n" not "<BR>"). In other words, HTML white space isn't properly handled
by multi-word message filters. To reproduce the problem, the source message text
has to have a line break between the search words -- this may not be visible in
Thunderbird but is visible in the mailbox source text.

Reproducible: Always

Steps to Reproduce:
1. Check the source mailbox text (the file where the mail text is saved) for a
unique pair of words in HTML with a line break ("\n" not "<BR>") in between.
2. Set up a filter on that mailbox for those words (using "Body" and
"Contains"). Use some verifiable action like "Move to folder".
3. Run the filter on that mailbox.

Actual Results:  
The filter action isn't performed.

Expected Results:  
The filter action should have been performed.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.