Sun Java System Communications Services 2005Q4 Release Notes

Compatibility Issues

The following table describes compatibility issues with Messaging Server:

Incompatibility 

Workaround 

Comments 

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.  

On Linux platforms, the Administration Console does not work for Messaging Server. 

Use the stop-msg and start-msg commands in the msg_svr_base/sbin directory.

For more information on the stop-msg and start-msg utilities, see the Sun Java System Messaging Server 6 2005Q4 Administration Guide.

After upgrading the Messaging Express Multiplexor (MEM) to version JES 4, the Unified Web Client default mailbox view has changed. 

(bug 6275916) 

No workaround. 

No additional comments. 

After upgrading Messaging Server to version JES 3, you see a null pointer exception when you try to start or stop Messaging Server through the Administration Server. 

(bug 6303859) 

Use the stop-msg and start-msg commands in the msg_svr_base/sbin directory.

For more information on the stop-msg and start-msg utilities, see the Sun Java System Messaging Server 6 2005Q4 Administration Guide.

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 2005Q4 Administration Guide.

While the preferred single-sign on (SSO) method is the one provided by Sun Java System Access Manager (formerly called Identity Server), Messaging Server continues to support the old version of single-sign on. 

No workaround 

For more information, see For more information on SSO and Access Manager, see: http://docs.sun.com/app/docs/coll/1292.1.

This release of Communications Express is incompatible with the 2004Q2 version of Calendar 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 Chapter 5, Sun Java System Communications Express 6 2005Q4 Release Notes.

The Communications Services Delegated Administrator console and utility (commadmin) are the preferred mechanisms for provisioning Messaging Server users in an LDAP directory that is compatible with Access Manager.

Though Access Manager services can be used to provision user and group entries, results with Access Manager are unpredictable and may negatively impact your deployment. Use the Communication Services Delegated Administrator instead. 

For more information on Delegated Administrator, see Chapter Chapter 4, Sun Java System Communications Services Delegated Administrator 6 2005Q4 Release Notes

Clarification is needed on RTF/HTML editing and browser compatibility for Messenger Express and Communications Express. 

(bug 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 2 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 3 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.