Move MailStore Gateway to new machine
Revision as of 11:09, 16 April 2024 by Lgodesberg (talk | contribs)
MailStore Gateway has multiple dependencies to network infrastructure. Depending on your specific setup, firewalls and DNS zones have to be re-configured as well.
MailStore Gateway behind a firewall
In this scenario it is assumed, that MailStore Gateway is exposed to the internet through a firewall. It does not matter, whether the firewall only does port-forwarding or acts as reverse proxy.
To move MailStore Gateway to a new machine, please follow the steps below:
- Create a backup of your OLD machine.
- Install MailStore Gateway on the NEW machine.
- The download can be found here [1].
- On the NEW and machine start the MailStore Gateway Config Tool by clicking on the desktop shortcut MailStore Gateway.
- On the NEW machine stop the Gateway service by clicking Stop Service.
- On the NEW machine close the MailStore Gateway Config Tool.
- On the NEW machine navigate into the folder C:\ProgramData\MailStore and delete the Gateway sub-folder.
- Log in the web interface of the OLD machine and suspend all mailboxes.
- Copy the folder C:\ProgramData\MailStore\Gateway from the OLD machine to the NEW machine.
- If using a third-party TLS certificate, copy and install the certificate to the NEW machine.
- Reopen the MailStore Gateway Config Tool from the desktop of the NEW machine and verify your settings. Especially that of the email domain and the certificate. Re-configure Let's Encrypt, if necessary.
- Start the MailStore Gateway Service on the NEW machine.
- Log in the web interface of the NEW machine and activate all mailboxes.
- Adjust firewall settings to forward Gateway traffic to the NEW machine.
- Adjust DNS settings, if necessary.
- Ensure the NEW machine is receiving mails.
- Archive the remaining mails from the OLD machine.
- Adjust the archiving profiles in MailStore Server to point to the new Gateway.
- Adjust email client settings to point to the new Gateway if used as email proxy.
- Decommission the OLD machine.
MailStore Gateway directly exposed to the internet
When MailStore Gateway is exposed to the internet directly, e.g. when running in Azure, AWS or GCP, follow the steps below. For a faster migration, it might be beneficial to lower the TTL of the MX record of the Gateway email domain that points to the old machine:
- Create a backup of your OLD machine.
- Install MailStore Gateway on the NEW machine.
- The download can be found here [2].
- On the NEW and machine start the MailStore Gateway Config Tool by clicking on the desktop shortcut MailStore Gateway.
- On the NEW machine stop the Gateway service by clicking Stop Service.
- On the NEW machine close the MailStore Gateway Config Tool.
- On the NEW machine navigate into the folder C:\ProgramData\MailStore and delete the Gateway sub-folder.
- On the OLD and machine start the MailStore Gateway Config Tool by clicking on the desktop shortcut MailStore Gateway.
- On the OLD machine stop the Gateway service by clicking Stop Service.
- Copy the folder C:\ProgramData\MailStore\Gateway from the OLD machine to the NEW machine.
- If using a third-party TLS certificate, copy and install the certificate to the NEW machine.
- Start the MailStore Gateway Service on the OLD machine.
- Reopen the MailStore Gateway Config Tool from the desktop of the NEW machine and verify your settings. Especially that of the email domain and the certificate. Re-configure Let's Encrypt, if necessary.
- Start the MailStore Gateway Service on the NEW machine.
- Adjust DNS settings, the MX record of the Gateway email domain must point to the NEW machine. Adjust the TTL in case it has been altered beforehand.
- Ensure the NEW machine is receiving mails.
- Archive the remaining mails from the OLD machine.
- Adjust the archiving profiles in MailStore Server to point to the new Gateway.
- Adjust email client settings to point to the new Gateway if used as email proxy.
- Decommission the OLD machine.
