User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 Thunderbird version 126.96.36.199 (20060909) Filters behaving badly in Thunderbird 188.8.131.52 (and very likely in Seamonkey) Running a filter from the "Tools->Run Filters on folder" and/or from the filters dialog box using "run selected filter(s) on: folder" look at the header description as well as data represented by that header... the same filter looking at new messages coming into a folder only looks at data in the header... If you create a filter that is supposed to look at the "Subject:" header, where you look to see if the header contains the text 'subject', then apply this filter manually to a folder, it will find EVERY message, not just the messages that contained the word 'subject' in the actual subject. The same filter operates as would be expected on new messages coming into the folder that the filters are enabled to be applied to automatically. That is the only messages filtered will be those that actually have the word 'subject' somewhere in the actual subject text. This same behavior exists will ALL headers, not just the "Subject" header, and this includes 'customized' headers as well. Reproducible: Always Steps to Reproduce: 1. Create a filter that looks messages that contain the text 'subject' included the header known as "Subject". Use any 'action' you like. Enable this on the 'inbox' of your email account. 2. Send yourself, or have someone send you email with the subject line something like "How do you like this subject". 3. Wait for the message to arrive and observe the expected 'action'. 4. Go to the menu item 'tools->Run Filters on Folder' and observe the behavior. Actual Results: Step 3, performs the action ONLY on messages that have the word 'subject' in the data contained in the subject data. Step 4 performs the action on ALL messages in the folder. Expected Results: Step 4, should perform exactly like Step 3 does... The filters looking at 'headers' look at the header itself and the data represented by the header, when performed manually. They should only look at the data represented by the 'header', as they do when you automatically apply the filter.
I'm not able to reproduce this with TB 184.108.40.206 or branch/trunk builds.
WFM also (trunk). Glenn do you still see this problem with 220.127.116.11 using profile where this is the only filter?
Version: unspecified → 1.5
Marking as WFM based on comment #1 and comment #2.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.