Closed
Bug 403001
Opened 18 years ago
Closed 18 years ago
Thunderbird doesn't filter messages correctly, if header line is wrapped
Categories
(MailNews Core :: Filters, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 124641
People
(Reporter: askwar, Unassigned)
Details
Attachments
(1 file)
|
3.78 KB,
message/rfc822
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.1.8) Gecko/20071023 Firefox/2.0.0.8
Build Identifier:
I've setup a mail filter in Thunderbird, which filters away certain messages based on what's in the subject. Recently I noticed, that this filter doesn't seem to work anymore.
Reproducible: Always
Steps to Reproduce:
1. Create filter with the only rule of "Subject" "contains" "Wegwerfbare E-Mail Adresse erfolgreich erstellt"
2. Action: Add Tag "Important" (or whatever...)
3. Apply the filter
Actual Results:
The message, which I'll attach as a file, isn't filtered.
Expected Results:
It should be filtered.
As written above, the rule has:
Wegwerfbare E-Mail Adresse erfolgreich erstellt
As soon as I trim that to
Wegwerfbare E-Mail Adresse
the filter applies again. I guess that's so, because in the header of the mail, you'll find:
Subject: [TrashMail] Wegwerfbare E-Mail Adresse
erfolgreich erstellt.
As you can see, there's a wrap after "Adresse" and before "erfolgreich".
| Reporter | ||
Comment 1•18 years ago
|
||
I'm using Thunderbird 2.0.0.6 on Linux.
Component: General → MailNews: Filters
Product: Thunderbird → Core
Version: unspecified → 1.8 Branch
| Reporter | ||
Comment 2•18 years ago
|
||
Updated•18 years ago
|
QA Contact: general → filters
Comment 3•18 years ago
|
||
Current bug summary of Bug 124641 is for still remaining problem of Bug 124641.
> Bug 124641 Filter or Search: do not handle multi-line (wrapped, folded) headers correctly when search term spans lines
DUPing to Bug 124641 is appropriate.
Updated•18 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•18 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•