378449 - Message filters : Filter rule with date can't be saved

Status: RESOLVED WORKSFORME

(MailNews Core :: Filters, defect)

Description

[Hideo Oshima]

If filter rule is defined with date,
it is not saved.

Steps to reproduced:
1. Open Message Filters.
2. Click New button.
3. Click combo box labed with "Subject" and select "Date".
   You can see date like "04/23/2007".
4. Set "Perform these actions" to anything you like.
5. Click OK.
6. Select "Filter Name" you made by above way, and click "Edit" button.

Actual result:
Date field is missing.
Expected result:
Date field is "04/23/2007" or something.

I observed with 2004042304-trunk/Linux build.

Comment 1

[Magnus Melin [:mkmelin]]

See this too. In the error console I get:

Error: time.getFullYear is not a function
Source File: chrome://messenger/content/dateFormat.js
Line: 167

... which is here http://lxr.mozilla.org/seamonkey/source/mailnews/base/resources/content/dateFormat.js#167

Comment 2

[WADA:World Anti-bad-Duping Agency]

Problem is that '\"date\"'(for cutomized Date: header) in msgFilterRules.dat is reset to 'date'(for pre-defined 'Date').
This is observed with Tb 2.0.0.6.
(1) msgFilterRules.dat contains following.
    condition="OR (\"date\",contains,2101)"
(2) Start Tb 2.0.0.6, Tools/Message Filters, Close "Message Filters" window
    (no need to edit filter rule)
(3) Content in msgFilterRules.dat is replaced by;
    condition="OR (date,contains,15-Jun-17148)"
Because changed to 'date', this rule is treated as rule for pre-defined Date(for date value saved in mail DB, not string data of Date: header). Then "contains" will be changed to "is" and value will be changed to date format when the rule is edited, and incorrect date value will become garbage.

I couldn't observe above problem with Tb trunk 2007/12 build.
condition="OR (\"date\",contains,2101)" was always kept when current trunk nightly.
=> WORKSFORME.

Note:
Although filter rule is kept correctly, filter rule on Date: header itself didn't work(doesn't fire) with Tb trunk 2007/12/19 build.
It is different issue from this bug.

Comment 3

[Wayne Mery (:wsmwk)]

I think wada forgot to change this to WORKSFORME. If anyone still sees this problem using v3, please reopen the bug.