CHAPTER 1 |
Upgrade and Migration Updates |
This chapter describes issues or updates for upgrading or migrating from SIMS 3.x to SIMS 4.0.
Note - Go to http://sun.com/sims/ for updated release notes and other product information concerning the Sun Internet Mail Server 4.0 (SIMS).
Several aspects of SIMS 4.0 differ significantly from the previous SIMS release. In particular, the provisioning model has undergone substantial changes, partly to accommodate the hosted domain features. For information on migrating from SIMS 3.x to SIMS 4.0, please contact your Sun representative or authorized Sun support provider. See http://sun.com/service/contacting/index.html for information on contacting Sun and http://internet.central.sun.com/service/support/index.html for information on Sun's support services.
SIMS no longer keeps a master copy of the shared folder that only the owner can access or update. Instead, each member of the distribution list has her own private copy which can be updated independently, and the owner needs to be a member to access to her own copy. Master copies of shared folders in a SIMS 3.x message store will no longer be accessible once the system is upgraded to SIMS 4.0. These shared folders should be moved or deleted using the imdeluser command.
For each shared folder to be removed (the list of these folders can be obtained by listing the contents of /var/opt/SUNWmail/ims/shared/*), run the imdeluser command using the SIMS Administrator credentials and specifying the shared folder name in place of a user to delete. This will remove the master copy of the shared folder but preserve each member's private copy.
To move a 3.x shared folder:
| 1. | If the owner was not a member, make the owner a member of the distribution list so she can have her own shared folder copy after the upgrade. |
| 2. | Locate the UNIX directory containing the master copy of the shared folder: |
| /var/opt/SUNWmail/ims/shared/*/shared_folder_name |
| 3. | Locate the UNIX directory containing the owner's folders: |
| /var/opt/SUNWmail/ims/user/*/username |
| 4. | Move (UNIX mv) the master copy under the owner shared space. For example: |
| % mv /var/opt/SUNWmail/ims/shared/212/sharedfolder/INBOX |
| /var/opt/SUNWmail/ims/user/155/owner/shared/sharedfolder |
| 5. | Remove (UNIX rm) the remaining UNIX directory which contained the master copy For example: |
| % rm -rf /var/opt/SUNWmail/ims/shared/212/sharedfolder |
The syslog format for the SIMS 4.0 Message Store and Message Access (MSMA) logging entries has changed since the SIMS 3.5 release. If you have written scripts for parsing the syslog file, be aware of these changes so you can update your scripts as well as take advantage of the additional information provided.
For example, the 3.5 MSMA syslog format for login messages was as follows:
Sep 17 15:11:51 desert imaccessd[<pid>]: Login user=<uid> host=<hostname>
where,
<pid> is the process ID of the program issuing the message.
<uid> is the user ID of the client.
<hostname> is the client hostname string.
The 4.0 MSMA syslog format for login messages is now:
Apr 29 08:53:49 desert SUNWmail.ims.imaccessd[<pid>]: <protocol>[<tid>]: Login user=<uid+domain_id> host=<hostid>
where,
imaccessd changes according to the program issuing the message. For the login/logout messages represented here, the program is imaccessd.
<pid> is process ID of the program issuing the message.
<protocol> may be either pop3, pop3s, imap, imaps depending upon the protocol and use of SSL.
<tid> is the thread ID of the thread within the process issuing the message.
<hostid> is the client IP address when the ims_client_lookup attribute in ims.cnf is set to DNSOFF (DEFAULT). When ims_client_lookup is DNSON <hostid> is the client hostname string.