Sun Java Communications Suite 5 Release Notes

Messaging Server Compatibility Issues

To purge users with iPlanet Delegated Administrator when you are running Messaging Server 6.3, see Purging Users with iPlanet Delegated Administrator and Messaging Server 6.3

The following table describes compatibility issues with Messaging Server:

Incompatibility	Workaround	Comments
`comm_dssetup.pl`, the program that prepares the directory server for Messaging Server (Calendar Server and Delegated Administrator) has been modified to work with both Directory Server 6.0 and Directory Server 5.x: Interactive Mode: Server-root and Directory Server Instances	Directory Server instance(s) reside in the server-root, or an explicit Directory Server instance directory Previous versions of Directory Server used the notion of a server-root where multiple instances and configuration info would be housed. Directory Server 6 no longer uses a server-root. Instances may be anywhere. In this question, a user needs to: 1) specify the instance directory. Or, if the user is using previous versions of Directory Server, the user can: 2) specify the server-root directory where the instances are housed. You will be prompted with an additional question to pick an instance from the server-root. Or, 3) a user who has used Directory Server 5x and is now using Directory Server 6 might manually put all of her Directory Server instances under a parent directory (what we used to call a server-root). Note – Server-root terminology has been removed from Directory Server 6.	no additional comments
`comm_dssetup.pl`, the program that prepares the directory server for Messaging Server (Calendar Server and Delegated Administrator) has been modified to work with both Directory Server 6.0 and Directory Server 5.x: Silent Installation: server-root directory	In previous versions of Silent installation, you would specify both a server-root and an instance directory. If you are using Directory Server 5.x, this still holds true. Since there is no server-root directory in Directory Server 6.0, you will need to specify the parent directory of the Directory Server instance.	no additional comments
The location of the Directory Preparation Tool `(comm_dssetup.pl)` has changed.	`comm_dssetup.pl` is now in its own package installed in `/opt/SUNcomds` for Solaris, and `/opt/sun/comms/dssetup` for Linux Existing scripts that specify the old path need to be updated.	To install the package, be sure the Directory Preparation Tool is selected in the appropriate installer panel.
In Messaging Server 5.x, an administrator could use the IMAP `list` command to display all folders in the message store. In a typical message store, this caused the server to display an unusually long list. In Messaging Server 6.x, when an administrator runs the IMAP `list` command, it displays only the explicitly shared folders.	To list all folders in the message store, use the `mboxutil` utility.	For more information on the `mboxutil` utility, see the Sun Java System Messaging Server 6.3 Administration Guide.
The configuration program for the Delegated Administrator has changed.	Install Delegated Administrator and run the configuration program. The current program is located at: for Solaris, `/opt/SUNWcomm/sbin/config-commda` for Linux `/opt/sun/comms/config-commda`	Upgrade to the new Delegated Administrator when installing this version of Messaging Server.
Upgrading Messaging Server with Webmail over IMAP protocol change (6397425, 6397451, 2137362)	The back-end server must be upgraded before upgrading the front-end server. Both the Webmail over IMAP protocol as well as the back-end message stores must be the same product version. See the Sun Java Communications Suite 5 Upgrade Guide for details.	no additional comments
This release of Communications Express is incompatible with the previous version of Messaging Server.	If you upgrade Communications Express, you must also upgrade Messaging Server.	This also applies to Calendar Server. For more information on Communications Express, see Chapter 6, Sun Java System Communications Express 6.3 Release Notes.
Clarification is needed on RTF/HTML editing and browser compatibility for Messenger Express and Communications Express. (6311363)	On Messenger Express, you are able to use RTF/HTML editing for Internet Explorer browsers. You are unable to use RTF/HTML editing with Mozilla or Netscape browsers. In the JES 2004Q2 version of Communications Express, you are able to use RTF/HTML editing for Internet Explorer browsers. You are unable to use RTF/HTML editing with Mozilla or Netscape browsers. In the JES 2005Q1 version of Communications Express, you are able to use RTF/HTML editing for Internet Explorer 5.5 or later, Mozilla 1.3 or later, or Netscape 7.2 or later.	No additional comments.
`"session.timeout` Login Again” pop-up error displays when you click Communications Express in Portal Server. (6417988)	Ignore the pop-up error, close the window, and continue to use Communications Express.	No additional comments.
If you use Messaging Server with Access Manager Single Sign-on, it does not support Java Enterprise System 2004Q2 Access Manager Server. However, Access Manager 6.3 and later is supported.	The specific versions of Messaging Server that do not support Java Enterprise System 2004Q2 Access Manager Server are: Messaging Server 6.2-6.01 and later Messaging Server 6.3	Upgrade Access Manager (JES 2004Q2) before upgrading Messaging Server.
Access Manager now has two installation types: Realm (version 7.x style) and Legacy (version 6.x style).	If you are installing Access Manager with Messaging Server, Calendar Server, Instant Messaging, Delegated Administrator, or Portal Server, you must select Legacy mode (version 6.x style). See: Sun Java System Access Manager 7 2005Q4 Release Notes	If the wrong Access Manager is installed, you will not be able to run Delegated Administrator.

Purging Users with iPlanet Delegated Administrator and Messaging Server 6.3

If you are using iPlanet Delegated Administrator and you upgrade to Messaging Server 6.3, you cannot use the imadmin user purge command to remove users from the directory as you did with earlier versions of Messaging Server (6486836). Instead, follow the steps shown below to purge users.

This compatibility issue occurs because the Administration Console and Administration Server have been removed in Messaging Server 6.3. With earlier versions of Messaging Server, you can continue to use imadmin user purge as before.

Note –

iPlanet Delegated Administrator, originally used with Messaging Server 5.x, is a deprecated utility. It is not the same tool as Communications Suite Delegated Administrator, introduced with Messaging Server 6.x. Communications Suite Delegated Administrator supports Schema 2. iPlanet Delegated Administrator supports Schema 1. (Some administrators who have upgraded Messaging Server to 6.x, but remain in Schema 1, have continued to use iPlanet Delegated Administrator to provision users.)

To purge Messaging Server 6.3 users with iPlanet Delegated Administrator

Apply iPlanet Delegated Administrator patch 1.2p3.

You can download this patch at the following site:

http://www.sun.com/download/index.jsp?cat=Collaboration%20%26%20Communication&tab=3

Go to the Delegated Administrator 1.2 Patch 3 for Messaging. This patch enables the imadmin user purge command to operate in a way compatible with Messaging Server 6.3. Follow the remaining steps in this procedure to enable the new behavior.

Modify the MsgSvrN-adminurl property in the iPlanet Delegated Administrator resource.properties file.

The MsgSvrN-adminurl property sets the url of the Administration Server. When this property is set to an actual url, the imadmin user purge command will attempt to locate the Administration Server, which will not respond. The imadmin user purge command will return an error.

You must set MsgSvrN-adminurl to this value: NO_ADMIN_SERVER.

The resource.properties file is located by default in the following path:

iDA_Install_Directory /nda/classes/netscape/nda/servlet/resource.properties

Note –
Multiple Message Stores Upgraded to Messaging Server 6.3:

The value N in MsgSvrN-adminurl is a variable that must be replaced with a specific value, such as 0, that identifies the message store system that has been upgraded to Messaging Server 6.3. If you have deployed multiple back-end message stores in Messaging Server 6.3, you must change this value for each instance of the MsgSvrN-adminurl property.

For example, if you have three back-end message stores, you must change this property in the resource.properties files for all three stores. You would change, for example, the MsgSvr0-adminurl , MsgSvr1-adminurl, and MsgSvr2-adminurl properties.

Multiple Message Stores Using Different Versions of Messaging Server:

Suppose you have deployed multiple message stores and have upgraded only some stores to Messaging Server 6.3, while others remain in previous versions of Messaging Server. In this case, change the MsgSvrN-adminurl property only for the stores upgraded to Messaging Server 6.3.

When you run the imadmin user purge command on a store for which you changed the MsgSvrN-adminurl property to NO_ADMIN_SERVER, the command will operate in the new way described in Step 5, below.

When you run the imadmin user purge command on a store where the MsgSvrN-adminurl property is unchanged (still pointing to an Administration Server url), the command will operate as it has in the past.

Restart the Web Server to which you have deployed iPlanet Delegated Administrator.

The Web Server on which iPlanet Delegated Administrator is running must be restarted to enable the changes in the resource.properties file to take effect.

Use the imadmin user delete command to mark the user as deleted.

imadmin user delete sets the inetUserStatus attribute to “deleted”. To delete multiple users, use the -i option. For example:

imadmin user delete -D chris -L user1 -n siroe.com -w bolton

Use the msuserpurge command to remove the user's mailbox.

msuserpurge finds all user entries where inetUserStatus or mailUserStatus are set to deleted, purges those user mailboxes from the message store, and sets mailUserStatus to removed. For example:

msuserpurge -d domain

You must run msuserpurge before you perform the next step (removing the user entry from the directory), or the user's mailbox will be orphaned.

You can schedule the msuserpurge command with the configutil parameter local.schedule.userpurge. For example:
configutil -o local.schedule.userpurge -v "30 2 * * 0 /opt/SUNWmsgsr/lib/msuserpurge -g 20"
In the preceding example, msuserpurge will run on Sundays at 2:30 a.m. It will remove the mailbox of every user marked for deletion longer than 20 days.

Use the imadmin user purge command to remove the user entry from the directory.

In earlier releases, this command performed the following actions:
1. Searches the directory for users marked as deleted.
2. Deletes each user's Personal Address Book from the directory.
3. Deletes each user's mailbox from the message store.
4. If the user's inetUserStatus attribute is set to deleted, the user entry is removed. If the user's mailUserStatus is set to deleted, the mail attributes are removed from the entry.
Now, because you modified the MsgSvr0-adminurl property, the Administration Server is not called. A message informs you that the Administration Server is not invoked. Step c, above, is not performed. The mailbox was already removed by msuserpurge in Step 3.

In Messaging Server 6.3, if the user's mailuserstatus has been set to removed (by msuserpurge) and no other services are present in the user entry, the imadmin user purge command removes the user entry from the directory.

If the attributes of another service such as calendar service are present in the user entry, the entry is not removed.