Local folders truncated on NS 4 profile migration

RESOLVED EXPIRED

Status

MailNews Core
Profile Migration
--
critical
RESOLVED EXPIRED
16 years ago
10 years ago

People

(Reporter: Bill Burton, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

(Blocks: 1 bug, {dataloss})

Trunk
x86
Windows 2000
dataloss

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (Windows NT 5.0; U)
BuildID:    2002053012

Profile Migration from NS 4.76 truncates local folders.  Some of my folders are 
rather large with several thousand messages.  One folder with over 7000 messages 
only had the first 2000 migrated, another with 16,700 messages only had the 
first 1200 migrated.  Another smaller folder with 1500 messages only had the 
first 250 migrated.

Reproducible: Didn't try
Steps to Reproduce:
This assumes there is at least one local folder in NS 4.x that's 2000 messages 
or more.  
1. Start Mozilla with no existing profiles to enable the Profile Migration. 
2. Select appropriate options to migrate profile from NS 4.x.
3. After migration completes, start up both Mozilla and NS 4.x and don't login 
to IMAP/POP mailbox to prevent any new mail from being delivered.
4. Compare sizes of migrated local folders by clicking on each folder and 
comparing the number of messages between NS 4.x and Mozilla.  For any folders 
that were not completely migrated, select the folder in Mozilla, sort it by date 
to see where the migration stopped.

Actual Results:  Many of the migrated folders have lost thousands of messages 
each with the migration for each folder stopping at some point between 300 and 
2000 messages.

Expected Results:  Contents of the migrated folders should be identical to those 
in NS 4.x with the same message counts.

Updated

16 years ago
Keywords: dataloss

Updated

16 years ago
Blocks: 123929

Comment 1

14 years ago
Two questions
1) "Reproducible: Didn't try"
Shouldn't you first try to reproduce the problem before submitting a bug?
2) Can you still reproduce the problem with a recent Mozilla version?
Product: MailNews → Core
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.