Closed Bug 889988 Opened 13 years ago Closed 12 years ago

Message filters do not catch all applicable messages first time run

Categories

(Thunderbird :: Filters, defect)

17 Branch
x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: greywolf, Unassigned)

Details

(Keywords: testcase-wanted)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 (Beta/Release) Build ID: 20130206152201 Steps to reproduce: [Platform: Fedora Core 16 (64-bit)] Mailbox has a large number of messages in it (>10,000). Created a (bunch of) filter(s) Ran each one individually. These filters mostly do not perform any action on a message except to tag it for visibility and/or future action. Example: Match All of the following: Subject | begins with | Backup: AND Subject | ends with | ly (log) AND Tags | is empty Perform the following actions: Tag | 7 EXP7 [I'm the IT department, and my boss chews off more of my arm every time I fail to catch critical user problem messages, so I am attempting to avert disaster by making the important messages easier to see thru the noise, and to make transient messages a little more easy to wipe out on a regular basis.] Actual results: Some messages which should have been affected (tagged) by the filter(s) in question were not. I had to re-run the filter quite a few times before all applicable messages got tagged. Mostly it fails to tag messages whose headers are not in the scope of the header window. Expected results: It should have caught and tagged them all on the first run.
Component: Untriaged → Filters
Greywolf, we need testcase messages to analyse this, pls remove/replace sensitive data from msg source and "add an attachment" above > Mostly it fails to tag messages whose > headers are not in the scope of the header window. Can you explain what you mean here, or add screenshots?
Keywords: testcase-wanted
sorry to close, but needs more info.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.