Very often it is essential to switch to the new server without any interruption in the services you provide.
If you install the new CommuniGate Pro server on the same system as the old mail server, you should:
- switch CommuniGate Pro SMTP receiving to port 26, so it will not interfere with your old server SMTP activity.
- switch CommuniGate Pro POP service to port 111, and IMAP service to port 144, so they will not interfere with your old server POP/IMAP activity.
- Configure CommuniGate Pro and create Domain Aliases and/or full featured Secondary Domains.
- Create some test accounts in the main and secondary domains and check that you can log into those accounts using WebUser Interface.
- Check that you can send mail from those accounts using the WebUser Interface: mail to other test accounts in the created domains and mail to other servers should be delivered correctly.
- If you have a POP or IMAP client that allows you to specify a non-standard port number, check that you can log into the. test accounts on POP port 111 and IMAP port 144.
- Create tab-delimited file(s) with names, passwords, and other attributes of your existing accounts and use the Account Import feature to create all accounts on your new server.
All this can be done while your old server is still active.
Now you should stop your old server activity by either changing its port numbers to non-standard values, or by disconnecting it from the external network.
Use the AccountMove program to copy all messages from your old server to CommuniGate Pro.
When all messages are copied, change the CommuniGate Pro SMTP port number back to 25, POP port number to 110, and IMAP port number to 143. Now CommuniGate Pro will operate as your mail server, without any interruption in the services you provide.
You may want to keep the old server running for several hours - in case its queue contained some delayed outgoing messages. Just check that the old server does not try to use the standard ports.