Closed
Bug 244375
Opened 21 years ago
Closed 21 years ago
MSF files regenerated when time zone changed
Categories
(MailNews Core :: Database, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 244358
People
(Reporter: peter, Assigned: Bienvenu)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
I recently travelled to a different time zone and back, and changed the time
zone settings on my laptop on arrival and on return. On both occasions all of my
MSF files were regenerated by the system, apparently without looking at the old
files, and as a result information about e.g. which messages had already been
read was lost - the same symptoms as for bug 231735 plus all of my junk mail was
marked as not junk.
Reproducible: Always
Steps to Reproduce:
1. Change Windows 2000 time zone setting
2. Open Mozilla
3. Open any folder
Actual Results:
The MSF file for that folder is regenerated. Certain messages which had been
read (including those imported from cc:Mail via Outlook) are marked as unread.
Junk mail in the junk mail folder is marked as not junk.
Expected Results:
Continued to use the old MSF file, perhaps with adjustments to time and date
information.
Comment 1•21 years ago
|
||
*** This bug has been marked as a duplicate of 244358 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•21 years ago
|
||
(In reply to comment #1)
>
> *** This bug has been marked as a duplicate of 244358 ***
The problem here is that I refreshed my view of this bug, in Mozilla 1.6, (with
the intention of checking whether any responses had been received) and Bugzilla
seems to have taken that as a resubmission of the bug with the same data. So
perhaps this is another bug, but maybe one already reported.
Updated•21 years ago
|
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•