Closed
Bug 186212
Opened 22 years ago
Closed 22 years ago
Filtering rules seem not stored correctly so change at next run of Mozilla making filters unuseable
Categories
(MailNews Core :: Filters, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 183158
People
(Reporter: swsolutions, Assigned: naving)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 While creating (or changing) a filter for Inbox, after saving the filter, the rule(s) should not change (obviously). In this Mozilla rev (and I notice this only in this rev) after a restart some rules are changed causing execution of filters with unwanted rules. Reproducible: Always Steps to Reproduce: 1.Start creation of a new message filter: Tools/Message Filter/New 2.Select in the appropriate rule's fields: "Status", "is", "Read" 3.Select in the appropriate action's fields: "Move to Folder", "Trash" (it can be any other folder) 4.Click on [OK] 5.Close the message Filters Dialog 6.Quit the entire Mozilla apps (Navigator, Composer, Mail etc.) 7.Restart Mozilla mail Actual Results: Opening again the Message-Filter/Filter-Rules box, the rule fields now show: "Status", "is", "Replied" (instead of the selected "Read") and the filter acts consequently. Replied messages are trashed instead of Read ones. This malfunction, in some cases/rules-combinations, may cause unexpected loss of data (messages). Expected Results: Mozilla should not make autocton changes in the rules fields. Any further attempt to correct the filters has no different result. The Mail Filters are unuseable.
There is an existing bug about Status criteria... will look up the bug number.
Didn't find the original issue I'm thinking of, but this is a duplicate of bug 183158 *** This bug has been marked as a duplicate of 183158 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•