216113 - Message filters created under release 1.2.1 lost when upgrading to 1.3 & 1.3.1.

Status: RESOLVED EXPIRED

(MailNews Core :: Filters, defect)

Description

[Kenneth Roznovsky]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425

Message filters created under release 1.2.1 are lost when upgrading to 1.3 &
1.3.1.  Message filters created prior to release 1.2.1 are kept when upgrade is
completed.

Reproducible: Always

Steps to Reproduce:
1. Created message filters prior to release 1.2.1.
2. Created many filter using 1.2.1.
3. Downloaded & executed 1.3 and/or 1.3.1 upgrades.
4. Upon reviewing message filters in 1.3 or 1.3.1 version all filters created
under 1.2.1 were missing.   

Actual Results:  
Message filtering with filters created under 1.2.1 no longer occurs.

Expected Results:  
All message filters should be visible in 1.3 and/or 1.3.1.

Comment 1

[Kenneth Roznovsky]

Attachment: Some of the message filters created using mozilla 1.2.1

Comment 2

[Kenneth Roznovsky]

Attachment: Message filters available after Upgrade to 1.3 and/or 1.3.1.

The filters in this JPEG image were created prior to upgrading to 1.2.1.  I
know this because all the missing filters were created within the last week or
so.  This bug is preventing me from upgrading to 1.4.

Comment 3

[Jeff lane]

Same thing here when upgrading to 1.4.  Have two different installations. One at
home was running 1.2.1 on Red Hat 9, and one at work running 1.2.1 on Red Hat 9.

After upgrading to 1.4, ALL of my message filters on every mail account
disappear.  Same thing happened at home.

Comment 4

[Asa Dotzler [:asa]]

->mailnews

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.