This section describes how to convert a SIMS mail server to a message access proxy/message access server. We will use the hypothetical example of an administrator migrating a number of users on the original SIMS mail server to a new SIMS server, and converting the original SIMS mail server to a proxy/message access server (FIGURE A-4 on page 289). The basic steps for completing these steps are as follows:
| 1. | Install new SIMS machine. | |
| 2. | Convert the old SIMS machine to a proxy/mail server. | |
| 3. | Establish the new machine a slave LDAP server to master server on the old machine. | |
| 4. | Disable mailbox accounts of users who are to be migrated so that mail sent to these users will be put on hold until the accounts are restarted. | |
| 5. | Using the command imbackup and imrestore, migrate the users from the old machine to the new machine. | |
| 6. | Change the Mailhost attribute in the entries of the migrated users | |
| 7. | Enable the disabled mailbox accounts so that they can receive mail. | |
| 8. | Delete all the migrated accounts from the old machine. |
| |
To Migrate Users by Converting a Mail Server to a Proxy/Mail Server |
In this example the original mail server to be converted to a proxy/mail server is called quackadero, and the new pure mail server is called quasi. The company is Adagio.
| 1. | Install new SIMS server. |
| 2. | Convert the old SIMS mail server to a proxy/mail server. |
FIGURE A-14 Admin Console (Sun Message Store->Advanced Options)
| 3. | Configure the new machine as an LDAP slave server and the old machine (now proxy/mail server) as an LDAP master server. |
| Follow the instructions described in "To Configure the Proxy Slave and Master Directories" on page 291. |
| 4. | Disable mailbox accounts of users who are to be migrated so that mail sent to these users will be put on hold until the accounts are restarted. |
Note - After completing this step, mail will not be delivered to the message queue and clients of this IMTA will not be able to send mail. Messages sent to these users will be bounced back to the sender or held at another MTA. The IMTA will be disabled until you run imta start dispatcher (step 8).
| a. | Shutdown the IMTA dispatcher. |
| # imta stop dispatcher |
| b. | Deliver all queued mail. |
| Run imta cache -view to view entries for queued mail. |
| Run imta submit [channel name] to queue mail. |
| 5. | Migrate mailboxes from one machine to another. |
| a. | Identify users to be moved to the new machine and have these users log out of their mail clients. |
| They must not use their mail client until after migration is complete. |
| b. | Use imbackup -f bak -u username_file to backup the mailboxes to be migrated. |
| bak is the name of the file in which to back up the mailboxes. username_file is a file containing a list of user names to be migrated. Each name must be separated by spaces, tabs, or carriage returns. See the SIMS Reference Manual for details. |
| c. | Use imrestore -t3 -f bak -u username_file to restore the backed up mailboxes to the new SIMS machine. |
| 6. | Change the Mailhost attribute in the entries of the migrated users. |
| You can do this from the Admin Console by modifying a group entry. See To Modify a Group Entry, Step 2, Section c. You can also use the ldapmodify command if you prefer to do this in a UNIX script. See the SIMS Reference Manual for ldapmodify details. |
| 7. | Delete all the migrated accounts from the old machine. |
| Log in to the old machine. As root, use imdeluser -u <username_file>. Do not run this command on the new machine or you will delete all your migrated users. See the SIMS Reference Manual for details. |
| 8. | Enable the disabled mailbox accounts so that they can receive mail. |
| a. | Synchronize the alias databases. |
| # imta dirsync -F |
| b. | Start the IMTA dispatcher. |
| # imta start dispatcher |
Proxy/mail server should be running as planned.