Migrating your mailbox from ISG to Exchange
Some professorships and institutes at D-ITET have decided to use the exchange mail server instead of the D-ITET mail server. This guide is intended to show you the steps to be able to move your mail account to the exchange server. If certain steps in these instructions are unclear, please contact your technical contact first or create a ticket by sending an email to <firstname.lastname@example.org>.
There are some limitations on the Exchange Server which mean that not all emails can be transferred. You must have completed the following steps before you start the actual migration itself:
Quota - In contrast to our mail server, your mailbox on the exchange server has a quota. This quota applies to your mailbox and all folders in it. Employees usually have a storage space limit of 5GB on the exchange server. If your technical contact tells you that you need to reduce the amount of data, you can either delete emails you no longer need or you can export them first, before you delete them afterwards. In Thunderbird you could use the following steps to export emails:
- Right click on the respective mail and select "Save as ..."
- Select the storage location. The mail is saved as an .eml file, which is opened and displayed again in Thunderbird with a double click.
- Afterwards you can delete the email.
If you have to export a lot of emails, you should use an export tool. For Thunderbird there is for example the ImportExportTools NG by Christopher Leidigh which can export many selectable mails in addition to the EML format also in PDF, HTML or plain text. You can find short instructions for this plugin here
Mail item limit - Every object on the Exchange server (email, contact, appointment entry, etc.) is an item. The Informatik Dienste have defined an upper limit of 50,000 items. Above this limit, performance problems can and will occur with your own mail account. If your technical contact tells you that you need to reduce the mail items, you can either delete emails you no longer need or you can export them first and then delete them. The steps to export your mails are the same as described under quota.
Single mailsize limitation - The maximum size for a single email is 20MB on the exchange server. This limit includes the header, mail text and base64 encoded binary data (which are increased by a factor of about 1.5!). If your technical contact tells you that you have oversized emails, you can either delete them or you can export them first and then delete them. The steps to export oversized emails are the same as described under quota.
You can carry out the steps mentioned above at any time. But please do only carry out the following steps one day before or on the day of the migration at the earliest. Before the account can be migrated, you may have to delete existing forwards on the exchange server and set up new forwards on the ISG mail server. These forwards are necessary in order to receive the mails on the exchange server until the final changeover of the domain to the exchange server.
Remove any IAM forward
By default we set a forward on the exchange server so that you would not miss any mail sent to your IAM account directly. This forward needs ro be removed. To do so execute the following steps:
Login with your username and password
Click Self Service and Manage forward to adjust your forward settings.
Remove any content in the Recipient Field and make sure Save and forward mails is not set. Then click Save.
Set a forward on the ISG mailserver
After removing the IAM forward you need to set a forward to the exchange server. The simplest way to do so is by using roundcube:
Login with your username and password
Select Settings and then Filters
By default you would see the isgdefault Filter set. This set contains the two rules Deduplicate and Vacation. Click the Create Button in the upper right frame and create a sieve rule like in the picture. Replace username in the action field with your username. Afterwards click Save.
From this moment on, every incoming email will be redirected to the exchange server. To be able to read any new email you either need to login with your credentials at the exchange webinterface https://mail.ethz.ch/owa or you need to configure a mail client to access the exchange server. If you used thunderbird on our server you should switch to Microsoft Outlook to access the exchange mailserver. Please refer to the Instructions / FAQ / How To / Tips Section on the ETH Mailbox Service Website to find instructions on how to configure a mail client to use the exchange mailserver.
Prepare an SSH-Client
Prepare an SSH-Client like openssh (linux/mac) or PuTTy (windows) to be able to carry out the synchronization with the assigned credentials (visible on the migration day in the Migration webinterface).
configuring PuTTy on Windows
On our managed machines you should find PuTTy in the list of applications or by clicking the Windows Button in the left bottom frame and typing putty. If you are using a self managed machine install PuTTy from https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html .
PuTTy opens a pop-up window. In the Basic Settings make sure to add login.ee.ethz.ch into the Hostname line, the port is set to 22 and the Connection Type is SSH.
Select the Window Category on the left side and make sure to use 150 for Columns and 50 for Rows.
Select Window/Translation Category on the left side and make sure to use ISO-8859-1:1998 (Latin-1, West Europe) for the Remote character set.
Click Open on the bottom of the pop-up window to establish a connection. Do not login with your personal credentials! Use the migration credentials from the webinterface instead!
Using openssh on linux / mac
Open a terminal and use the following command. Replace migruser by the migration user assigned to you (as seen in the webinterface). The password can also be found in the webinterface, but only on the day of migration.