Closed
Bug 65651
Opened 24 years ago
Closed 24 years ago
offer facility to import mail from multiple NS 4.x profiles into the one NS6/Mozilla profile
Categories
(MailNews Core :: Profile Migration, enhancement)
MailNews Core
Profile Migration
Tracking
(Not tracked)
People
(Reporter: dave532, Assigned: sspitzer)
References
()
Details
A posting on n.p.m.general was asking if there was a way to import mail from
multiple communicator profiles into the one Mozilla profile. This is because
NS4.x only supported single POP3 account and Mozilla supports multiple accounts
so they used to use multiple profiles to manage the mail when want to take
advantage of this feature and manage all their mail under one profile.
Two ways of implementing this:
1) An advanced option when migrating the profile from Netscape 4.x saying
something like "Would you like your mail from all communicator profiles imported
into a single profile?"
2) The import utility will have the option to import Communicator mail (at the
moment it only does Outlook and Endora), it would then pop up a list of profiles
you'd like to import from and you can select one or many profiles.
In fact I believe 2 should be implemented because the import utility doesn't
offer to import communicator mail at present and if someone wants to create a
fresh profile they may still want to import their Netscape mail.
Original news posting by: Alan Liddle <adl@adlsoftware.com>
Comment 1•24 years ago
|
||
Why not simply drag and drop your 4x mail folders into your mozilla profile?
These are text files and I do this manual transfer all the time, but without the
*.snm files.
Assignee | ||
Comment 2•24 years ago
|
||
this is a duplicate, I logged it a while back. I think it is currently owned by
nobody@mozilla.org
Comment 3•24 years ago
|
||
This is the dupe.
*** This bug has been marked as a duplicate of 13832 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
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
•