User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 With 2 of the 6 mail accounts I have created, none of the filters for these accounts will run, either when mail is received, or if I try to manually run one filter or all filters on any folder (inbox or other) for that account. One feature that is common between these 2 mail account's filters and the other mail account filters (that run just fine) is that I created a customized filter header and then made a filter on that header. Reproducible: Always Steps to Reproduce: 1. Select a message in the inbox and view full headers. Select a value in the header to filter on (such as the Delivered-To: header) and copy. Click on Message and then "create filter from message" (from the menu options on the top toolbar). 2. In the create filter dialog, select the Customize option and create a new header value to filter on (such as Delivered-To), then "contains", then enter the value copied above in the 3rd box, creating a filter rule. 3. Select a folder to filter the mail into, and click OK (creating the filter). 4. Highlight the filter you have just created (without deactivating it), the folder you want filtered (the folder containing the message in step 1), and click on Run Now. Actual Results: The filter fails to run. There is no progress bar, there is no filtering. Expected Results: Filtered the messages according to the header and values entered in step 2, moving the message(s) into the indicated folder selected in step 3. The system hangs while not running the filter. It affects not just mailnews, but the browser as well, so it's more than a minor annoyance if you have just created a filter that should filter dozens or hundreds of emails, and you want to do something else while it's filtering, and instead you have a hung system.
similar behavior in Mozilla 1.3a Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
JC Dill, is this bug still a problem for you? Have you tried upgrading to a more current version of Mozilla (1.3 or 1.4)? I have successfully run filters on custom headers in both those versions. If you are still running Mozilla but no longer have this problem, please resolve the bug as WorksForMe.
=>WFM, no response from reporter.