Sun Java System Messaging Server 7 Update 1 Release Notes

These Release Notes contain important information available at the time of the general release of Sun Java System Messaging Server 7 Update 1 including:

About Messaging Server 7 Update 1

Messaging Server is a high-performance, highly secure messaging platform that can scale from thousands to millions of users. It provides extensive security features that help ensure the integrity of communications through user authentication, session encryption, and the appropriate content filtering to reduce spam and viruses. With Messaging Server, enterprises and service providers can provide secure, reliable messaging services for entire communities of employees, partners, and customers.

Messaging Server provides a powerful and flexible solution to the email needs of enterprises and messaging hosts of all sizes by using open Internet standards.

What's New in This Release of Messaging Server

See the What's New document.

Deprecated and Removed Features for Messaging Server

Support for the following features may be eliminated in a future release, have already been removed in this release, or were removed in a previous release:

DIGEST-MD5

When clients connect via IMAP, POP or SMTP to the Messaging Server, they must use a SASL (RFC 2222) authentication mechanism or a simple password to prove their identity to the server. When the LDAP directory is configured to store user passwords in the clear, all user passwords are migrated to this format and the sasl.default.ldap.has_ plain_passwords option is set on the Messaging Server, then three additional authentication mechanisms are enabled: APOP, CRAM-MD5 and DIGEST-MD5. All three of these mechanisms transmit a one-way encoding of the password over the wire rather than the password itself. Due to its limited deployment and complexity, the DIGEST-MD5 mechanism is deprecated leaving only the APOP and CRAM-MD5 mechanisms.

imsimta refresh

This command has been deprecated. Use imsimta cnbuild in Sun Java System Messaging Server 6.3 Administration Reference and imsimta restart in Sun Java System Messaging Server 6.3 Administration Reference instead, as appropriate.

MMP Section and Instance features

The optional SECTION and INSTANCENAME features of the ServiceList MMP configuration parameter are deprecated and will be removed in a future release. These features make the MMP configuration more complex than necessary and it is believed the more commonly used virtual domain feature of the MMP provides sufficient configuration flexibility.

Direct Editing of MTA Databases

MTA access to database files and the imsimta tools to manipulate MTA database files are deprecated.

Netscape Browser Support

Netscape browser support will be removed at a future date.

Red Hat Linux 3 Support

Red Hat Linux 3 platform support has been deprecated in this release and will be removed in a future release. Communications Suite 6 continues to be supported on Red Hat Linux 4.

Event Notification Service (ENS)

In this release, there are two notification services for event notifications and alarms: Sun Java System Message Queue (JMQ) and Event Notification Service (ENS). For this release, Calendar Server, and Instant Messaging still have internal dependencies to ENS; therefore, you can continue to use ENS. By default, ENS is not enabled in this release. To enable ENS, set local.ens.enable to 1.

Prior to Messaging Server 7, if you wanted to use IMAP IDLE, you had to configure an ENS notification plug-in. In this release you can use JMQ to provide IMAP IDLE notifications.

You can use JMQ for message notifications by configuring a JMQ notification plug-in. (Messaging Server allows you to configure multiple notification plug-ins.) To enable JMQ notifications, see, Enabling JMQ Notification.

Ignored imta_tailor settings

As part of a future project to support an XML configuration, the MTA's tailor file is in the process of being deprecated. As previously documented, some options in that file should not have been edited or otherwise changed. With this release of Messaging Server, only eight options in that file are honored. All other options specified in the tailor file are ignored, even if they were set to non-default values. The eight options which are still honored are IMTA_LANG, IMTA_RETURN_PERIOD, IMTA_RETURN_CLEANUP_PERIOD, IMTA_RETURN_SPLIT_PERIOD, IMTA_TMP, IMTA_USER, IMTA_USER_USERNAME, and IMTA_WORLD_GROUP.

Requirements for Messaging Server 7 Update 1

See Requirements for Communications Suite 6.

Note For information about upgrading to Messaging Server 7 Update 1 from a previous version of Messaging Server, see Messaging Server Installation Notes.

Messaging Server Installation Notes

These installation notes pertain to the Messaging Server 7 Update 1 release. This section contains the following subsections:

Installation Overview for Messaging Server

Use the Communications Services installer to install Messaging Server.

For installation instructions, see the Communications Suite 6 Update 1 Installation Guide.

Next, you must configure Messaging Server by:

• Running the Directory Server Preparation Tool, comm_dssetup.pl .
• Running the Messaging Server configuration program.

For configuration instructions, see the Communications Suite 6 Update 1 Initial Configuration information.

comm_dssetup.pl Changes for this Release

The following changes were implemented in the latest version of comm_dssetup.pl, the program that prepares Directory Server for Messaging Server use:

1. Silent Installation: password change
   -w dirmanager_passwd has been deprecated in favor of -jpasswd_file
2. See Messaging Server Compatibility Issues for more changes to the comm_dssetup.pl program.

Upgrade Instructions for Messaging Server

If you are upgrading to Messaging Server 7 Update 1 from an earlier release, follow the upgrade instructions in the Communications Suite 6 Update 1 Upgrade Guide.

Checking the /etc/hosts file entry

If you are installing Messaging Server for the first time or upgrading from an earlier version of Messaging Server, ensure that you have your host's IP address in the /etc/hosts file, for example:

129.158.230.64 budgie.siroe.varrius.com budgie

Note On Solaris OS 10 U3 and earlier platforms, you not only have to add the Fully Qualified Domain Name (FQDN) to the /etc/hosts file, but also to the /etc/inet/ipnodes file. Otherwise, you will get an error indicating that your host name is not a Fully Qualified Domain Name. From Solaris OS 10U4 onwards, the contents of the /etc/inet/ipnodes and /etc/hosts files have been merged together into just the /etc/hosts file. Applying kernel patch 120011-14 on any Solaris 10 system will also perform the merge, and subsequent removal of the /etc/inet/ipnodes file.

Messaging Server Documentation Updates

There are no Messaging Server Documentation Updates at this time.

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/sun/comms/dssetup for Solaris and 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 listcommand 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 and Linux, opt/sun/comms/da/bin/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
Communications Express 6.3 is incompatible with versions of Messaging Server prior to 6.3.	If you upgrade Communications Express, you must also upgrade Messaging Server.	This also applies to Calendar Server. For more information on Communications Express, see Sun Java System Communications Express 6.3 Release Notes.
Clarification is needed on RTF/HTML editing and browser compatibility for Communications Express. (6311363)	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.
SNMP MADMAN mib support in Messaging Server 6.3 and later	Running on Solaris 9 or earlier, Messaging Server SNMP support requires the Sun SEA SNMP master agent which comes with Solaris. There are issues with the SEA master agent. The preferred solution is to upgrade to Solaris 10 or later and use the Net-SNMP which comes with the OS. Running on Solaris 10 or later, Messaging Server SNMP support requires the Net-SNMP which comes with the OS.

Problems Fixed in This Release of Messaging Server

6686339

When imap.numprocesses is set to 10, IMAP flag updates are not working in an IDLE session.

6648157

Messaging Server upgrade from 6.3 to 7.0 has one diff3 error in the imta_tailor.new file.

6569452

The following mailbox database error message can be displayed: "Environment reference count went negative."

6654364

The IMAP server closes down a client's connection after the fetch command.

Known Issues and Limitations in Messaging Server

This section describes known issues in the Messaging Server product.

6780552

In the French version, some apostrophes are missing from some OLH pages in the GUI configurator.

6759556

MeterMaid does not work as expected in case that quota value exceeds quota_time.
Workaround
In order to ensure proper functionality of MeterMaid, set the value of metermaid.table.tablename.quota to a value that is less than metermaid.table.tablename.quota_time Note that tablename is a placeholder for your own table name.

6726739

Metermaid integer overflow occurs with a large quota:time ratio

No Issue ID

After an upgrade, when you restart the server, the Berkeley Database issues a log version error, issuing the following message: 'Skipping log file...historic log version.'

Redistributable Files for Messaging Server

The following redistributable files are provided with Messaging Server 6.x:

• You can redistribute the following files in source (HTML and Javascript) or binary form (GIF files) within a licensed Messaging Server distribution only:
  • msg-svr-base/config/html (and subdirectories)
  • msg-svr-base/install/config/html (and subdirectories)
    You are not permitted to distribute these files by themselves.

• You can copy and use (but not modify) the following header files solely to create and distribute programs to interface with Messaging Server APIs, to compile customer written code using the documented API to interoperate or integrate with Messaging Server, and only as expressly provided in the Messaging Server documentation:
  • msg-svr-base/examples/meauthsdk/expapi.h
  • msg-svr-base/examples/tpauthsdk/authserv.h
  • All files in the msg-svr-base/include directory (default location)

• The following files are provided solely as reference for writing programs that use the documented API to integrate with Messaging Server:
  • msg-svr-base/examples/meauthsdk/
  • msg-svr-base/examples/tpauthsdk/
  • msg-svr-base/examples/mtasdk/