Windows Live Mail To Outlook
Christelle Stdenny
I have looked at a windows live to pst converter - maybe I need to use a program for that if I cant export from Windows Live Mail into an exchange format. I am really unsure of how to get the imported emails onto the server after getting them into Outlook.
What I ended up doing before your reply was install Live Mail onto another PC that had Outlook installed, import the eml files into that instance of Live Mail and then export that to Outlook. I then exported the data as a PST file that I plan on importing into Outlook on the first machine. A bit of a pain, but needed to be done.
Question - after I import the PST file into Outlook, will Outlook upload these emails onto the IMAP server? Or will they only be local in the PST file? I would really like to get rid of any email storage on my local machines and want them to sit on the server.
2 of the accounts are imap and can be moved with ease. there is a 3rd account setup in live mail that does not sync with a server and only serves to store about 8000+ messages dating from 2009 to 2015. The messages are on the hard drive of the old laptop in .eml format.
I created a .pst file in outlook to house the older mail. What I need to know is how to import it. I tried dragging and dropping it from the hard drive into the outlook folder and it imported, but was not treated as a mail message showing info like from, to, date, message. Outlook treated it as a file with todays date.
Please first understand here we mainly focus on general issues about Outlook desktop client and know little about Windows live Mail. As I know, there may be no option in Outlook that could import the .eml file directly except dragging it to the folder.
However, based on my research, I found a relevant article that mentioned we could install the Outlook in original PC and import your message from windows live mail to Outlook directly, then we could export a .pst file in Outlook and restore it in your new PC. For more detailed information, please refer to the Scenario 2: Outlook is located on another computer and Migrate Mail part of the article mentioned above.(Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.)
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Do you still have any questions about it?
If not, in order to close this thread normally, please kindly mark the helpful post to answer, which would benefit others who also has similar issues.
Thanks for your understanding.
I tried to export from Windows live mail to outlook and it keeps hanging on message 21 of 7007. The first 20 went into outlook without failure. I can see the folder with email in the windows explorer. How do I know which item is #21. I thought about removing a few messages at a time till i get rid of the offending item, but that would take forever since it could be any of the 7000+ messages.
Try exporting a smaller batch of messages (e.g., 50 or 100) at a time instead of all 7007 messages at once to see if you can find the problematic email message that way. In this manner, you can identify the problematic message(s) and fix the issue.
I suspect that this is caused by having the wrong email client set as
default. Change the default email client and see if that helps.
And BTW, you may experience corruption because importing a pst file into
Outlook can cause this. All you needed to do is to OPEN the pst file in
Outlook.
MAPI doesn't exist unless a MAPI client is installed. Outlook Express
and Windows Mail are not MAPI clients so they don't install the MAPI
libraries nor do they themselves provide that API interface. Outlook is
a MAPI client so its install provides the MAPI support. You're stuck
having to install Outlook to get MAPI support on the host where you want
to use MAPI to transfer messages. MAPI is just an API definition for mail, like SMTP is just a definition
for how to transfer messages. You need a program that does that
protocol or provides that API. You need Outlook installed so it can
handle the MAPI calls. An API needs a handler. For MAPI, that would be
Outlook.To do the transfer, Windows Mail will use MAPI but that's just an
interface to *something*. That something is the Outlook client. You
need to have Outlook installed so the MAPI commands sent to it have it
read the items from its .pst file to then transfer as data to whomever
made the MAPI call. There aren't many functions (just 12) in the Mail
Application Programming Interface (MAPI).If you don't want to install Outlook on your host (because you don't
want it to pollute your host or don't have a license for it), go back to
your friend's host where he had Outlook installed. He probably also has
Outlook Express installed there as well (hopefully he isn't using it;
else, he will have to copy his Identities folders so he can restore them
later). In the Identities folder where OE stores its .dbx database
files, delete them all: .dbx files for each folder and even the
folders.dbx file. Just delete all files under that identities
subfolder. On my Windows XP host, the default path for the OE store is
under:%userprofile%\Local Settings\Application
Data\Identities\sid\Microsoft\Outlook ExpressWhen you start OE the next time, you start with a fresh setup that is
devoid of any e-mails. OE will recreate the missing .dbx files. You
don't want to mix in your e-mails and folder hierarchy with whatever
might've been left in OE from prior use. Open OE and do the import from
Outlook. Then do an export from OE. Alternatively, rather than
exporting, you could just copy the Identities subfolder to your other
host and import using that as the source for the OE store.I wrote the above on-the-fly so steps might be missing on how to migrate
an OE message store from one host to another. There are plenty of
articles on how to do this as found in a Google search: =migrate+%2B"outlook+express"+another+computerThe idea is to use MAPI (which requires Outlook) on one host to get your
messages into OE. Then transfer OE's message store to another host so
you can import from it.MAPI is just an interface. Something has to actually support that MAPI
interface. That involves Outlook. _Application_Programming_Interface
-us/library/cc307725.aspx
Oops, missed your "I installed a borrowed copy of Outlook" statement.Still working on the MAPI error. It appears that WLM screwed it up (or
something done during setup or config caused the problem). Even when
right-clicking on the root node of the message store shown in the
folders pane and selecting Properties and then Advanced can generate
that error. Going to Internet Options -> Programs and selecting Outlook
as the e-mail client does not fix that error. Using the Help -> Detect
and Repair menu in Outlook doesn't help. The MAPI files have been
screwed up.I also installed WLM (and Outlook 2002 was previously installed). I get
the above error (for trying to get into the advanced properties. Also,
when I use the Mail applet in Control Panel and go to look at User
Profiles and click on Properties, I get the following error dialog:An exception occurred while trying to run
"C:\Windows\system32\shell32.dll,Control_RunDLL "C:\Program Files\Common
Files\System\Mapi\1033\MLCFG32.CPL",@0"(The outer pair of double-quotes are not part of the command, just used
to delimit the command string which itself uses double-quotes due to
spaces included in the path.) I created a new "test" profile (no accounts) and I can click on
Properties for it in the Mail applet. So my "Outlook" profile got
screwed up. I've seen many posts suggesting to create a new profile to
get around the corruption. I haven't seen any suggesting on how to
repair a corrupted profile.Mail profiles are listed under the following registry key:HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
Messaging Subsystem\ProfilesIn my case, I'm not sure the "Outlook" named profile is actually
corrupt. It looks like the command to get at it is invalid. Under the
registry key for the "Outlook" profile is a subkey named (for me):0a0d020000000000c000000000000046So I'm wondering if the parameters to the command to get at the profile
are wrong. At the end was "@0". Maybe it was supposed to be
0a0d020000000000c000000000000046 but I don't know where I could change
the parameters to the command.Still looking into it. I don't really want to define a new mail profile
and have to migrate all my e-mail, calendar, journal, and note items
from the old to new profile.
Yep, in my case (and maybe yours, too), the problem is with a corrupted
mail profile. To be specific, MLCFG32.CPL crashes when I try to look at
the Data Files configuration for the "Outlook" profile. Creating a new
mail profile doesn't result in this error.In my case, I can create a new mail profile and have it point at the old
.pst files for its data files (for the message store and my archive
store). The mail profile was corrupted, not the .pst file.In your case, and since you won't be keeping Outlook around or care
about the mail profiles, just see if creating a new mail profile gets
you past the problem. When you create a new mail profile, you specify
where to create the .pst file. Just point at your old .pst file. You
might also want to give the profile a unique name other than the defalt
of "Personal Folders" (since you can't tell which one you're picking to
use as the default mail profile if they all have the same name). Use
something like " - TempXFR". A corrupted mail profile is not the same as a corrupted .pst file.