On Demand Migration for Email Current - User Guide

Introduction Preparing Migrations Test and Pilot Migrations Configuring and Running Migrations Post Migration Glossary

Zimbra

Zimbra

Mail Routing between Zimbra and Office 365

To set up mail routing between Zimbra and Office 365, you must configure per-mailbox forwarding in conjunction with subdomain forwarding. This prevents email duplication and subdomains appearing in the Reply Address on any message, either internal or external.

To set up mail routing between Zimbra and Office 365:

  1. Configure both Zimbra and Office 365 to accept mail from the same domain, for example, “example.com”.

In addition, MX records point to Zimbra. Though MX can direct email at either system, it is best to have mail delivered to the server with the largest number of users. This means that at the start of the migration, MX points to Zimbra, and at the halfway point of the migration, the MX records switch to point to Office 365. Note that the system receiving the mail must know about all users in both systems.

The first step is to create two subdomains used for routing.

  1. Create an MX record for each domain, which allows each system to send mail to the other.

For example, the domain “O365.example.com” directs mail to Office 365, while the domain “zimbra.example.com” directs mail to Zimbra.

  1. After you create the MX records, set up each system to accept mail for the new subdomains.

For Office 365, you add this domain as a new Accepted Domain. In Zimbra, you add this as a new Domain.

For Zimbra, you must create aliases for this new subdomain under the Aliases section of Manage Accounts.

For Office 365, you must configure each user with the routing domain, either manually or via a powershell script.

  1. Create representative mailboxes in Office 365 for each user that is presently in Zimbra.

This allows users who are migrated to Office 365 to see a GAL that is populated with all the users, as well as facilitate message forwarding for users still homed in Zimbra.

  1. After all the users have mailboxes in Office 365, set forwarding on them that will remain until the user is migrated.

The setting of forwarding can be done with the ODME per-user mail forwarding feature, as described in the section Setting Up Mail Forwarding.

  1. When migrating users, flip forwarding so that new mail is delivered to the Office 365 mailbox, and not the Zimbra mailbox.

With the ODME per-user mail forwarding option, you now need to select to remove forwarding from the target as well as setting forwarding in the source. It is important to remove the target forwarding to prevent the creation of a mail loop

Mail Routing between Zimbra and Exchange 2010

To set up mail routing between Zimbra and Exchange 2010, you must configure per-mailbox forwarding in conjunction with subdomain forwarding. This prevents email duplication and subdomains appearing in the Reply Address on any message, either internal or external.

To set up mail routing between Zimbra and Exchange 2010:

  1. Configure both Zimbra and Exchange 2010 to accept mail from the same domain, for example, “example.com”.

In addition, MX records point to Zimbra. Though MX can direct email at either system, it is best to have mail delivered to the server with the largest number of users. This means that at the start of the migration, MX points to Zimbra, and at the halfway point of the migration, the MX records switch to point to Exchange 2010. Note that the system receiving the mail must know about all users in both systems.

The first step is to create two subdomains used for routing.

  1. Create an MX record for each domain, which allows each system to send mail to the other.

For example, the domain “ex2010.example.com” directs mail to Exchange 2010, while the domain “zimbra.example.com” directs mail to Zimbra.

  1. After you create the MX records, set up each system to accept mail for the new subdomains.

For Exchange 2010, you add this domain as a new Accepted Domain. In Zimbra, you add this as a new Domain Alias.

For Zimbra, you must create aliases for this new subdomain under the Aliases section of Manage Accounts.

For Office 365, you must configure each user with the routing domain, either manually or via a powershell script.

  1. Create representative mailboxes in Exchange 2010 for each user that is presently in Zimbra.

This allows users who are migrated to Exchange 2010 to see a GAL that is populated with all the users, as well as facilitate message forwarding for users still homed in Zimbra.

  1. After all the users have mailboxes in Exchange 2010, set forwarding on them that will remain until the user is migrated.

The setting of forwarding can be done with the ODME per-user mail forwarding feature, as described in the section Setting Up Mail Forwarding.

At this point, mail routing is configured and operational between Exchange 2010 and Zimbra.

  1. When migrating users, flip forwarding so that new mail is delivered to the Exchange 2010 mailbox, and not the Zimbra mailbox.

With the ODME per-user mail forwarding option, you now need to remove forwarding from the target as well as setting forwarding in the source. It is important to remove the target forwarding to prevent the creation of a mail loop.

GroupWise

GroupWise

Refer to the documentation provided by GroupWise for information on setting up mail routing.

Sun ONE/iPlanet

Sun ONE/iPlanet

Refer to the documentation provided by Sun ONE/iPlanet for information on setting up mail routing.

Initial Target Mail Hosts

Initial Target Mail Hosts

Refer to the sections below for mail routing instructions specific to your target email service.

Related Documents