Demo des CSS-Bildrahmens
|Deletions are marked like this.||Additions are marked like this.|
|Line 29:||Line 29:|
|Line 39:||Line 39:|
Migrating your mailbox from ISG to Exchange
- 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 <email@example.com>.
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 central IT Service (ID) has 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. To find emails larger 20MB you can use the following steps in Thunderbird:
While Thunderbird is open, press CTRL-SHIFT-F or select Edit -> Find -> Search Messages.
Create a Rule named: Size (KB) is greater than 20480
Press the Search Button to find the Mails. If you have a lot of large Mails, it could make sense to press Save as Search Folder. In that case a virtual Folder will be created containing all large emails.
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 to 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.
Together with the technical contact of an institute, the ISG creates a list of the users to be migrated and sets a migration date for each account. As soon as the migration begins, all users can log in with their credentials at https://mmigr.ee.ethz.ch . In this interface you can see:
- The accounts you need to migrate (most people will only see their own username here)
- The day on which your migration is planned
- Your migration credentials (username/password) to access the synctool. These credentials can only be seen the day your migration is planned.
- Link to this instruction website
Before you start the synchronisation process, make sure you have followed all Pre-migration steps!
Login to the https://mmigr.ee.ethz.ch and make sure to write down the username and the password for the migration account.
Enter the accountname which needs to be migrated (testuser in the example). Mostly this will be your own username only.
Select 1 if you use the same password on both server (Applies to most users!) or 2 if you have different passwords.
If you selected 1 you can enter the password.
If you selected 2 you need to enter separate passwords for each mailserver
The credentials you entered will be checked against both servers. If everything was correct, you will be presented one of the two menus. The left one will be seen if you never migrated this account before, the right one, when you already snychronized the account and need to resync.
Start now to synchronize your account by choosing sync or resync. While the mail account gets synchronized, you will see the progress of the tool.
When the synchronisation has finished you will see some overview
- Do not worry, when there are Mails on the host2 (exchange server) which can not be found on our ISG server (host1). This only means that your configured forwards work and that there are some mails on exchange which have never been saved on the ISG mailserver.
If there were no problems while the account was synced, you will see Detected 0 errors.
When the sync has errors
When you have finished your synchronisation you will see this menu
You can select analyze to let the tool check for the most common (mostly harmless) errors:
In the best case there were no errors at all
Sometimes some mails could not be transfered because they are too large for the exchange mailserver. In that case you need to delete or export the email (see Pre-migration steps). The error will show two screens. The left gives you some information, the right one shows, which mails had the problem.
When you get the message, that some folders were not selectable, do not worry. This is only an informational message and not a real error. You can ignore these messages. <<BR>
If the tool finds some critical error you could try to resync. But if the same error occurs again, you should contact ISG as stated in the screenshot.
Check the logfile
When you select showlog from the mainmenu you can see the last logfile created in this session. Use it to check the created logfile by yourself.
The showlog commando is the only one, where you can scroll through the entire logfile.
If you had no problems while syncing the data you are finished with your syncrhonisation:
Please do not change any of the forwards and IAM settings or you could break the mail receiving
- Inform your technical contact, that every went well and that your account is synchronized.
- From now on, use the configured mail client (Outlook is recommended by ID) on the exchange server.
If you had problems contact first your technical contact and if he can not help, inform ISG by creating a ticket. Write an email with your problem to <firstname.lastname@example.org>.