Figure 1: Enable POP / IMAP protocol for users.
2. As mentioned in Part 1, we can export the Mdaemon account list and use the columns in it to create a migration file. Open the
MDaemon Console , select
Accounts | Exporting , then click
Export accounts to comma delimited file .
- We can use the dump file from MDaemon to create the file that the Microsoft Transporter tool needs to use, we can use Excel or a simple editor like Notepad to change the format. In the table below we can see all Transpoter tool columns to use and we have used that dump file from MDaemon.
Column SourceIdentity
Column SourceIdentity Email SourceServer - SourceLoginID Mailbox SourcePassword Password TargetIdentity -
- A second option is to use the Import-Mailbox command to retrieve data from a PST file to transfer to an existing Exchange mailbox. This method can be useful if the user does not have any data on the Mdaemon server and all information is stored in their local PST file. In this situation, using the Microsoft Transporter tool will not work because it only copies data from the Mdaemon server and then switches to the Exchange server.
- The third method is to perform migration on the workstation. If the user is using Outlook Express, we need to install the Outlook client and then move the data. If the user is using an Outlook PST workstation, you just need to move the data to the new server.
In this series, we have explored some of the steps for each step used in the Coexistence conversion scenario to move data from Mdaemon mail server to Exchange Server 2007. Some of the procedures are covered in series. This article can be used on many third-party mail servers. Each third-party mail server has its own features and configurations, but the main operations are quite similar.
In the rest of this series we will perform some administrative tasks that the Mdaemon administrator needs to know in the Exchange Server 2007 environment.