Closed
Bug 14689
Opened 25 years ago
Closed 25 years ago
[DOGFOOD] [PP] POP migration fails to move local files
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M11
People
(Reporter: pmock, Assigned: sspitzer)
References
Details
(Whiteboard: [PDT+])
Build Date & Platform Bug Found:
MacOS seamonkey build 1999-09-22-09-m11 installed on G3/400 Mac OS 8.5.1
Overview Description:
When I migrate my nova pop3 profile to 5.0, my local mail folder are moved but
are not used. My server, nsmail-2, folder that contains my inbox, sent, etc
files are copied to my new profile folder Mail directory. Per Seth instruction
today, I modified my prefs.js and moved the line "# Mozilla User Preferences" to
the top of the file. When messenger was open, a server1 folder was created on my
hard drive and new inbox, sent, draft, etc folders were created.
Steps to Reproduce:
0) Create a Communicator 4.x pop profile
1) Delete your mozregistry.dat and previous profile
2) Double click on the script file Mozilla Installer
The migration profile dialog will appear
3) Select the profile you want to migrate and click the start button
Communicator may crash (different bug 14600). If not quit the program
4) Edit the prefs.js file
5) Delete the first line
6) Move the line "# Mozilla User Preferences" to the top of the file
7) Save changes then Start Apprunner again
The browser window appears.
8) Open Messenger
9) Expand the server list
10) Click on your inbox
The inbox is empty. It should contain the mail messages that were in your
4.x inbox.
Actual Results:
On the hard drive, my nsmail-2 folder was moved to the new profile but the
files were not copied/moved to the serverX folder.
Expected Results:
In Messenger, when I click on my migrated pop folders, I should see all my
messages that I had in 4.x.
Additional Builds and Platforms Tested On:
This problem does not occur on the Win32 1999-09-22-09-m11 build.
Additional Information:
According to Seth, he fixed part of the bug. He wanted me to log a bug as
placeholder for him. Note: I spoke with Leaf. There was only 1 optimized build
for Mac on 9/22.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Summary: [PP] POP migration fails to move local files to new serverX folder → [PP] POP migration fails to move local files
Assignee | ||
Comment 2•25 years ago
|
||
changing summary.
if you had a pop server in 4.x named nsmail-2, you should expect to see your
mail migrated to <profile>:Mail:nsmail-2 on the mac.
Assignee | ||
Comment 3•25 years ago
|
||
ok, I'm seeing it now.
on linux and nt, pop migration seems to work.
on mac, there seems to be a disconnect.
it moved the pop files to Mail:tintin, but it's looking for them in Mail:server1
damn.
Summary: [PP] POP migration fails to move local files → [DOGFOOD] [PP] POP migration fails to move local files
I'd like to recommend this bug for DOGFOOD usage for the PDT team to review. I
think that this bug is an important step to get Mac users internally to use
mail.
Assignee | ||
Comment 5•25 years ago
|
||
now that sfraser fixed the crash on startup, I can look at this bug again.
I agree its a dogfood bug. I got a couple I'm working on first, so it may be a
few days before I can get to this.
Updated•25 years ago
|
Target Milestone: M11
Comment 7•25 years ago
|
||
M11
Comment 8•25 years ago
|
||
Seth, should we hold M11 for this? Are you close?
Assignee | ||
Comment 9•25 years ago
|
||
this is one of many mac migration bugs that depend on 16551.
I can't really debug and fix until 16551 is fixed.
fixing dependency.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 10•25 years ago
|
||
marking fixed. migrating a 4.x pop account on the mac works.
note, migrating a 4.x imap account doesn't seem to migrate the "local mail" from
4.x, but that's another bug.
thanks to danm for fixing 16551.
Comment 11•25 years ago
|
||
OK using 1999-11-04-08m11 commercial build mac OS 8.5.1
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
•