Sun Java™ System Messaging Server
Release Notes for HP-UX

Version 6.2 2005Q1

Part Number 819-1570-10

These Release Notes contain important information available at the time of release of Sun Java™ System Messaging Server 6.2 2005Q1 for HP-UX. Known issues and limitations, and other information are addressed here. Read this document before you begin using Messaging Server 6.2 2005Q1.

The Messaging Server 6.2 2005Q1 release includes the following products and tools:

Messaging Server
Communications Express
Delegated Administrator

These release notes contain the following sections:

Release Notes Revision History
About Messaging Server 6.2 2005Q1
Bugs Fixed in This Release
Important Information
Communications Express
Delegated Administrator Utility
Known Issues and Limitations
Redistributable Files
How to Report Problems and Provide Feedback
Additional Sun Resources

Third-party URLs are referenced in this document and provide additional, related information.

Note	Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

---

Release Notes Revision History

Table 1  Revision History 

Date	Description of Changes
February, 2005	Initial release of Sun Java System Messaging Server 6.2 2005Q1 Release Notes for HP-UX
July, 2005	Release of RR version of Sun Java System Messaging Server 6.2 2005Q1 Release Notes for HP-UX

---

About Messaging Server 6.2 2005Q1

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 prevent 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.

This section includes:

What’s New in This Release
Hardware and Software Requirements

What’s New in This Release

The following new features and enhancements were added to the Messaging Server 6.2 2005Q1 release:

Sun Java System Communications Services 6 2005Q1 Delegated Administrator

The Communications Services 6 2005Q1 Delegated Administrator is a new graphical user interface (GUI) for provisioning Messaging Server users and mail services in an LDAP Schema 2 directory.

With Communications Services Delegated Administrator, you can provision users in an LDAP Schema 2 directory only. To provision Messaging Server users in an LDAP Schema 1 directory, you must use iPlanet Delegated Administrator, a deprecated tool.

Delegated Administrator has two user components:

Delegated Administrator console (graphical user interface)
Delegated Administrator utility (command-line utility)

In earlier releases, this utility was called the Communications Services User Management Utility (commadmin). In this release, it has been renamed Communications Services Delegated Administrator utility.

The command-line name that invokes the Delegated Administrator Utility remains the same: commadmin.

Online help in the Delegated Administrator console describes how administrators can use the GUI to provision users in an LDAP directory.

For information about configuring and managing Delegated Administrator, see the Sun Java System Communications Services 6 2005Q1 Delegated Administrator Guide.

Communications Express Mail supports Secure/Multipurpose Internet Mail Extension (S/MIME).

Sun Java System Communications Express Mail now includes the security advantages of the Secure/Multipurpose Internet Mail Extension (S/MIME). Communications Express Mail users who are set up to use S/MIME can exchange signed or encrypted messages with other Communications Express Mail users, and with users of the Microsoft Outlook mail system.

Information about using S/MIME is part of the online help for Communications Express Mail. Information to administer S/MIME is explained in the Sun Java System Messaging Server 6.2 2005Q1 Administration Guide.

Support for Symantec Anti-Virus Scan Engine using the Internet Content Adaptation Protocol (ICAP).
Enhanced logging, including the following:
Improved Control of MTA Debug Logging
Enhanced Connection Logging
Message Tracing for Message Store Logging (message lifecycle logging)
imexpire Enhancements
Added -u user option to expire one user
Added -m max_rule option to specify maximum number of rules
Added -r max_thread_partition option to specify maximum number of threads per partition
MTA Disk Availability Check

Administrators can configure the variable local.queuedir config to specify the MTA queue directory to be monitored by msprobe.

Variable Substitution for IMAP Quota Warning Message

The following variables are supported.

[ID] - userID

[DISKUSAGE] - disk usage

[NUMMSG] - number of messages

[PERCENT] - store.quotawarn percentage

[QUOTA] - mailquota attribute

[MSGQUOTA] - mailmsgquota attribute

Exclude Bulk Mailboxes from Backup

The configuration variable local.store.backup.exclude has been added to specify mailboxes to be excluded during backup.

Enhancements in the imquotacheck and mboxutil utilities

Added -t num option to mboxutil to list mailboxes which have not been accessed in num days.

Single User Reconstruct of Mailboxes Database

The -u user option was added to the reconstruct command.

LDAP Operations over SSL Based Connections

New configutil variables are provided to configure the server to perform LDAP operations over SSL.

local.ugldapusessl=yes

local.ugldapport=636

local.service.pab.ldapusessl=yes

local.service.pab.ldapport=636

Login ID specified via Search Filters

A %o in inetdomainsearchfilter or sasl.default.ldap.searchfilter expands to the user’s original login ID before UID and domain parts are separated.

POP Exclusive Access

You can configure configutil -o local.pop.lockmailbox -v 1 to only allow only one POP session at a time to access a mailbox.

Message Store Disk Availability Check

You can stop messages from being delivered to a message store partition when the partition fills more than a specified percentage of available disk space. You set two configutil parameters, local.store.checkdiskusage and local.store.diskusagethreshold, to enable this feature and specify the disk-usage threshold.

With this feature, the message store daemon monitors the partition’s disk usage. As disk usage increases, the store daemon dynamically checks the partition more frequently (ranging from once every 100 minutes to once a minute).

Enhancements in the imquotacheck and mboxutil utilities:

In Messaging Server 6.x, the old quotacheck utility has been renamed the imquotacheck utility.

In addition, duplicate features in the imquotacheck and mboxutil utilities have been consolidated so that each utility performs a unique and distinct function.

The imquotacheck utility delivers over-quota warning messages to end users; it can also list user quota information. The utility obtains information primarily from the LDAP directory.

The mboxutil utility performs a variety of message-store management and reporting functions; the utility obtains information primarily from the local mboxlist database.

The following options have been added to imquotacheck:

-a Lists all quota information. This option is the default behavior in imquotacheck.
-q Lists domain quota information. Now you can use imquotacheck -d domain.
-u Lists user information. Now you can use imquotacheck -u.

These options obtain a list of users from the LDAP directory, not the local mboxlist database.

In addition, the Messaging Server 5.x quotacheck user search, which used the mboxlist database, is deprecated.

In Messaging Server 5.x, when you used the quotacheck utility to retrieve a list of users, quotacheck searched the local mboxlist database. This function duplicated the list function in the mboxutil utility.
To retrieve a list of users from the local mboxlist database, use the mboxutil utility with the -l option.

The mboxutil utility generates a user list faster than imquotacheck, which uses the LDAP directory.

Enhancement in the reconstruct -m -p command.

In previous releases, if you ran reconstruct -m -p partition, the utility would do the following:

Scan the specified partition.
Fix the folder.db for users in the specified partition.
Fix the quota.db and lright.db for users in all partitions.

This behavior led to potential duplication if you ran multiple instances of reconstruct in parallel against different partitions. (Each instance would fix the entire quota.db and lright.db.)

In this release, if you run reconstruct -m -p partition, the utility does the following:

Scans the specified partition.
Fixes the folder.db for users in the specified partition.
Fixes the quota.db for users in the specified partition.

The command does not fix the lright.db because it would require scanning the acls for every user in the message store. Performing this operation for every partition is not efficient.

To fix the lright.db:

Run reconstruct -m -p partition1, reconstruct -m -p partition2, and so on.
Run reconstruct -l.

Restoring messages that have been incrementally backed-up.

If you want to restore messages from a mailbox that has been incrementally backed-up, and if that mailbox no longer exists, you must follow different restore procedures from previous releases. Refer to the Sun Java™ System Messaging Server Administration Guide.

Enhancement in the message store restore utility.

When a mailbox has been deleted or is being migrated, the imsrestore utility recreates the mailbox with the mailbox UID validity and message UIDs stored in the backup archive.

In the past, when imsrestore would recreate a deleted or migrated mailbox, it would assign a new UID validity to the mailbox and new UIDs to the messages. In that situation, a client with cached data would have to resynchronize the UID validity and UIDs. The client would have to download the new data again, increasing the workload on the server.

With the new imsrestore behavior, the client cache remains synchronized, and the restore process operates transparently, with no negative impact on performance.

(If a mailbox exists, imsrestore assigns new UIDs to the restored messages so that the new UIDs remain consistent with the UIDs already assigned to existing messages.)

To ensure UID consistency, imsrestore locks the mailbox during the restore operation.

However, because imsrestore now uses the UID validity and UIDs from the backup archive instead of assigning new UID values, UIDs could become inconsistent if you perform incremental backups and restores.

(If you perform incremental backups with the -d date option of the imsbackup utility, you might have to invoke imsrestore multiple times to complete the restore operation. If incremental backups were performed, you must restore the latest full backup and all subsequent incremental backups.)

New messages can be delivered to the mailbox between the restore operations. In this case, the message UIDs can become inconsistent.

To prevent inconsistency in the UIDs, take one of the following actions:

During the restore operation, disable delivery of messages to the mailbox.
Before you start the restore operation, create the mailbox with the mboxutil -c command.

Additional Message Store/Access minor features
Identify for routing purposes DSNs and MDNs
Enhanced Mappings with (optional) connection information
Further options on from: address rewriting
UTF-8 enabled in mapping tables
Message Views in Communications Express
Message Flags in Communications Express
Message Search Enhancements in Communications Express
Single Copy/Relinker for the Message Store
mgrpErrorsTo LDAP attribute

The mgrpErrorsTo attribute specifies either an email address or a URL, which is resolved to produce an address. The address is placed in the MAIL FROM (envelope from) field of all messages the list produces. Additionally, the presence of the mgrpErrorsTo attribute causes the MTA to treat the group as a full-fledged mailing list and not as a simple autoforwarder.

The basic purpose of the MAIL FROM address is to create a place to send reports of message delivery problems. As such, the main effect of mgrpErrorsTo is to cause errors delivering list mail to be directed to the mgrpErrorsTo address. (There are, however, other semantics associated with and uses of the MAIL FROM address that are described in the various messaging RFCs, most notably the SMTP specification RFC 2821 and the NOTARY RFCs 3461-3464. The latter RFCs also describe many of the additional semantics associated with mailing lists.)

msuserpurge replaces iPlanet Delegated Administrator command

The Messaging Server msuserpurge command replaces the deprecated imadmin user purge command (an iPlanet Delegated Administrator command-line utility for use with LDAP Schema 1 directories).

Mail filter .war files are automatically included in Communications Express.

After you install Messaging Server and run the configure program, you no longer need to enable a .war file to set up mail filters. Specifically, you do not need to deploy the MailFilter.war file via the Web container (./wdeploy deploy for Web Server or ./asadmin deploy for Application Server).

Messaging Server has introduced additional features and updates described in the sections that follow.

MTA Enhancements

New MTA features include the following:

The MTA now has the ability to process multiple LDAP attributes with the same semantics. The handling attributes receive depends on the semantics. The possible options are:
Multiple different attributes don't make sense and render the user entry invalid. This handling is the default unless otherwise specified for this release.
If multiple different attribute are specified one is chosen at random and used. LDAP_SPARE_3 is the only attribute that receives this handling in this release; it is how all attributes are handled prior to this release.
Multiple different attributes do make sense and should be treated as equivalent. This handling is currently in effect for LDAP_CAPTURE, LDAP_MAIL_ALIASES, and LDAP_MAIL_EQUIVALENTS.
The MTA now has the ability to chose between multiple LDAP attribute values with different language tags and determine the correct value to use. The language tags in effect are compared against the preferred language information associated with the envelope from address. Currently, the only attributes receiving this treatment are LDAP_AUTOREPLY_SUBJECT (normally mailAutoReplySubject), LDAP_AUTOREPLY_TEXT (normally mailAutoReplyText), LDAP_AUTOREPLY_TEXT_INT (normally mailAutoReplyTextInternal), LDAP_SPARE_4 and LDAP_SPARE_5.
MAIL FROM and RCPT TO commands that fail due to various syntax or wrong state errors now generate B records in the log just like bad commands do.
Sieve errors are now logged as such in mail.log when LOG_FILTER is enabled.
The defaultdomain channel keyword has now been completely removed. This was necessary to resolve a conflict with an identically named option in the MMP.
The MTA contains code that performs various fix-ups on messages. One of these fix-ups is to insert a From: field into the header when this mandatory field is missing. The value that is inserted comes from the envelope from (MAIL FROM) field. However, the code used to use the actual value that is going to end up in the envelope from field of the message, which in the case of a mailing list expansion is the error-reporting address. The code has been changed to insert the original envelope from field, so this information is not lost.
The mgrpAllowedDomain and mgrpDisallowedDomain attributes now support wildcards.
Domains are now canonicalized prior to performing the comparisons used to determine whether to use internal or external autoreply text.
Support for the Windows-125x character set (charset) has been added to Messaging Server.
A nonstandard refuse sieve action has been added.

This action can only be used in system-level sieve scripts. A single string argument is required. If used, this action causes the current message to be immediately rejected at the SMTP level. The string argument is returned as the error string in SMTP. Refuse is incompatible with all other sieve actions except for discard.

If an error occurs in a sieve filter, the sieve owner is notified that the sieve is broken. If it is not a user sieve, the appropriate postmaster is notified of the failure. The incoming mail is filed in the user’s INBOX.
Support has been added to the PMDF and SIMS APIs to allow tracking of intermediate addresses. This makes it possible for the ims-ms to use sensible addresses in DSNs rather than the internal final addressing forms the ims-master channel program requires.
Support has been added to the low-level logging and message dequeue code to track intermediate addresses. This provides the means for success DSNs to use sensible addresses in DSNs rather than channel-specific private final addressing forms.
Additional diagnostic detail has been added to SMTP responses that result from failed ETRN commands.
imsimta cnbuild can handle very large system sieves.
The MTA's address rewriting logic has been changed to handle alias expansion errors better. More specifically, address failures in a group or alias that does not override the envelope from would be silently ignored as long as at least one address in the group or alias was valid. The MTA has been changed so that such failures are now reported to the group or alias. A side effect of this change is that groups or aliases that do not contain any valid addresses will not be reported as such and not simply as an invalid address.
If the SMTP server cannot read the options file or finds an options-file syntax error, the channel program aborts and an error message is written to the log.
The alias processing machinery now keeps track of any personal name information specified in the attribute named by the LDAP_PERSONAL_NAME MTA option, and uses this information to construct From: fields for any MDNs or vacation replies generated.
The REJECT_RECIPIENTS_PER_TRANSACTION SMTP channel option now can be set usefully to values bigger than the ALLOW_RECIPIENTS_PER_TRANSACTION SMTP channel option. Also, the code now tracks attempts to add recipients in addition to tracking successful recipient additions, and uses this value in the REJECT_RECIPIENTS_PER_TRANSACTION comparison.
MTA now uses specialized machinery to keep track of whether or not a given address expansion result should be employed in DSNs and MDNs as a final recipient address. In addition, if the result should not be so employed, this machinery tracks the address that should be used.

The semantics of the various sorts of address expansions implemented through LDAP are well-defined and set this information automatically. Entries in alias files and databases, however, do not have such clear semantics and, in practice, are used for multiple purposes. A mechanism to explicitly call for a given expansion address to be hidden has therefore been added. Prefixing an expansion address with a colon causes it not to be used in DSNs and MDNs. The address input to the alias expansion operation will be used instead. An example of an alias file entry that uses this facility is:

a: :b@example.com

Some useful flags are now set prior to calling the FROM_ACCESS, SEND_ACCESS, MAIL_ACCESS, ORIG_SEND_ACCESS, and ORIG_MAIL_ACCESS mappings. These flags are:
$A: Set if SASL has been used.
$T: Set if TLS has been used.
$S: Set if success delivery receipts requested (not available in FROM_ACCESS).
$F: Set if failure delivery receipts requested (not available in FROM_ACCESS).
$D: Set if delay delivery receipts requests (not available in FROM_ACCESS).
The application information string supplied to the FROM_ACCESS, MAIL_ACCESS, and ORIG_MAIL_ACCESS mappings now includes the system name claimed in the HELO/EHLO SMTP command. This name appears at the end of the string and is separated from the rest of the string (normally “SMTP”) by a slash (/). (The claimed system name can be useful in blocking some worms and viruses.)
New USE_PERSONAL_NAMES and USE_COMMENT_STRINGS MTA options were added to optionally include source and destination channel information in PERSONAL_NAMES and COMMENT_STRINGS mapping probes.

Setting either option to bit 0 (value 1) will add the usual source-channel|destination-channel| prefix to the corresponding mapping probe.

Note that these new options do not control whether the PERSONAL_NAMES or COMMENT_STRINGS options are used; the PERSONAL_NAMES or COMMENT_STRINGS options are controlled by various channel keywords.

Per-user conversion tags are now applied before mail host information is considered, which enables front-end systems to perform user-specific conversion operations.

Note	The Communications Server Delegated Administrator is the recommended mechanism for provisioning Messaging Server and Sun Java System Calendar Server (Calendar Server) users. The Access Manager (formerly called Identity Server) Services (as described in the Sun Java™ Enterprise System Installation Guide at http://docs.sun.com/doc/819-0056) provide only minimal Messaging and Calendar Server LDAP user entry provisioning. Because the Access Manager Services interface does not provide input validation, user entries that cannot receive email or otherwise do not function will be created without reporting any errors. Consequently, we recommend using the Access Manager Services interface for demonstration purposes only.

Deprecated Features

Support for the following features may be eliminated in a future release:

Messenger Express and Calendar Express

Going forward, no new features will be added to the Messenger Express and Calendar Express user interfaces. They have been deprecated in favor of the new Communications Express user interface. Sun Microsystems, Inc. will announce an end-of-life time line for Messenger Express and Calendar Express at a future date.

Administration Console

The Sun Java System Administration Console has been deprecated and will be removed from the Messaging Server product in a future release.

Netscape Browser Support

Firefox browser support will replace Netscape browser support at some point.

Hardware and Software Requirements

This section specifies the hardware and software required for this release of Messaging Server. The table below lists hardware and software requirements for HP-UX operating systems

Table 2  HP-UX Hardware and Software Requirements

Component	Platform Requirement
Supported Platforms	HP-UX PA-RISC
Operating System	HP-UX 11i vi
RAM	1 Gbytes
Disk Space	500 Mbytes

The section describes the following platform, client product, and additional software requirements for this release of Messaging Server:

Supported Platforms
Client Software Requirements
Product Version Compatibility Requirements
Messaging Server Use of Administration Server
Additional Software Requirements
File System

Supported Platforms

This release supports the following platform:

HP-UX Operating System with required patches

For detailed information about HP-UX requirements, including required patches, see the
Sun Java Enterprise System Installation Guide ( http://docs.sun.com/doc/817-5760)

For a list of the Messaging Server packages, see “Appendix E: List of Installable Packages,” in the Sun Java Enterprise System Installation Guide ( http://docs.sun.com/doc/817-5760).

Note	The Java Enterprise System installer checks for required platform patches. You must install all required patches or the installation process will not continue.

Note	The performance of your Messaging Server depends on many factors, including CPU power, available memory, disk space, file system performance, usage patterns, network bandwidth, and so on. For example, throughout is directly related to file system performance. If you have questions about sizing and performance, contact your Sun Java System representative.

Client Software Requirements

For Messenger Express access, Messaging Server requires a JavaScript-enabled browser. For optimal performance, Sun recommends the browsers listed in the table below:

Table 3  Messaging Server 6.2 2005Q1 Client Software Recommendations 

Browsers	HP-UX
Netscape™ Communicator	7.0
Internet Explorer	5.5 or 6.0
Mozilla™	1.2 or 1.4

Product Version Compatibility Requirements

Messaging Server is compatible with the product versions listed in the table below:

Table 4  Product Version Compatibility Requirements 

Product	Version
Sun Java System Directory Server	5.1, 5.2
Sun Java System Access Manager (formerly called Identity Server)	6.1 (Command-line Interface Only)
Sun Java System Web Server	6.1 (with iPlanet™ Delegated Administrator)

NSS Version Requirements

Messaging Server 6.2 2005Q1 requires the use of the shared security component NSS version 3.9.3.

For more details about product version dependencies, see the
Sun Java Enterprise System Installation Guide ( http://docs.sun.com/doc/817-5760) and
Sun Java Enterprise System Release Notes ( http://docs.sun.com/doc/817-5503).

Messaging Server Use of Administration Server

Messaging Server uses Administration Server for the following purposes:

If you use the console to administer Messaging Server, you must have Administration Server running on the same machine.
When Messaging Server is configured, Messaging Server reads the Administration Server configuration files. However, Administration Server does not have to be running to accomplish this task.

Additional Software Requirements

A high quality caching DNS server on the local network is a requirement for a production deployment of Messaging Server. Messaging Server depends heavily on the responsiveness and scalability of the DNS server.

Additionally, ensure in your setup that DNS is properly configured and that it is clearly specified how to route to hosts that are not on the local subnet:

The /etc/rc.config.d/netconf should contain the IP address of the gateway system. This address must be on a local subnet.
The /etc/resolv.conf exists and contains the proper entries for reachable DNS servers and domain suffixes.
In /etc/nsswitch.conf, the hosts: line has the files, dns and nis keywords added. The keyword files must precede dns and nis.
Make sure that the FQDN is the first host name in the /etc/hosts file.

If your Internet host table in your /etc/hosts file has multiple line, like:

123.456.78.910 budgie.west.sesta.com 123.456.78.910 budgie loghost mailhost

change it to one line for the IP address of the host. The first host name should be a fully qualified domain name. For example:

123.456.78.910 budgie.west.sun.com budgie loghost mailhost

File System

The following file systems are recommended for message stores:

The NFS (Network File System) is recommended in the following situation:

Though NFS is not supported on machines with message stores, you can use this file system on MTA relay machines, particularly if LMTP is enabled, or for autoreply histories and message defragmentation. (See the Sun Java™ System Messaging Server Administration Guide (http://docs.sun.com/doc/817-6266) for more information on autoreply). In addition, NFS can be supported on BSD-style mailboxes (/var/mail/).

---

Bugs Fixed in This Release

None.

---

Important Information

This section covers the following topics:

Installation Notes
Compatibility Issues
Documentation Details for Messaging Server 6.2 2005Q1

Installation Notes

These installation notes pertain to the Messaging Server 6.2 2005Q1 release:

Installation Overview for Messaging Server

Use the Java Enterprise System 2005Q1 Installer to install Messaging Server.

For installation instructions, see the Sun Java Enterprise System 2005Q1 Installation Guide
( http://docs.sun.com/doc/817-5760).

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 “Chapter 1: Post-install Tasks and Layout,” in the Sun Java System Messaging Server 6.2 2005Q1 Administration Guide (http://docs.sun.com/app/docs/doc/819-0105).

Checking the /etc/hosts file entry

If you are installing Messaging Server for the first time, ensure that you have the following entry in /etc/hosts file on your HP-UX system:

<ip-of system> <FQHN> <hostname>

For example, 129.158.230.64 budgie.siroe.varrius.com budgie

Installation Overview for Delegated Administrator

To install Delegated Administrator, use the Java Enterprise System 2005Q1 Installer to install the following components:

Directory Server
Messaging Server
Web Server or Application Server
Access Manager

The Delegated Administrator software is installed together with Access Manager.

For installation instructions, see the Sun Java Enterprise System 2005Q1 Installation Guide
( http://docs.sun.com/doc/817-5760).

Next, you must configure Delegated Administrator by

Running the Directory Server Preparation Tool, comm_dssetup.pl. (If this script was run after Messaging Server was installed, you do not need to run it again.)
Running the Delegated Administrator configuration program, config-commda.

For post-installation configuration instructions, see the Sun Java System Communications Services Delegated Administrator Guide.

Compatibility Issues

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.

If you are running both the latest Communications Express (Universal Web Client) and the deprecated Messenger Express Web mail interface, the address books used by these two clients do not share information. If end users switch between the two client interfaces, the two address books will contain different entries.
Sun Java System Delegated Administrator (DA) is supported by Web Server version 6.1. If your LDAP directory is still in Schema 1, and you want to continue to provision mail users with DA, use DA with Web Server 6.0.
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.
The Communications Services user Management utility (commadmin) is the preferred mechanisms for provisioning Messaging Server users in an LDAP directory that is compatible with Access Manager.

The Access Manager Services provide only minimal Messaging and Calendar Server LDAP user entry provisioning.

The Access Manager Services interface do not provide input validation, so user entries that are not functional are created without reporting any errors. Use the Access Manager Services interface for demonstration purposes only.

Messaging Server provides the following two mail filters that work with different user interfaces:
The old mail filter provided through the Sun Java System Delegated Administrator interface
A new mail filter provided with Communications Express and Messenger Express

You cannot use both mail filters. If you use the mail filter functionality in Delegated Administrator, disable the mail filter in Communications Express or Messenger Express. Conversely, if you use the Communications Express or Messenger Express mail filter, you cannot use the mail filter functionality in Delegated Administrator.

Documentation Details for Messaging Server 6.2 2005Q1

These Release Notes are the only document published with the Communications Services 6.2 2005Q1 on HP-UX platform. Use the following URL to see all the Messaging Server 6.2 2005Q1 documentation:

http://docs.sun.com/coll/MessagingServer_04q2

Messaging Server 6.2 2005Q1 provides the following documents:

Sun Java System Messaging Server Release Notes.
Sun Java System Messaging Server Administration Guide
Sun Java System Messaging Server Administration Reference
Sun Java System Messaging Server Developer’s Reference
Sun Java System Messaging Server Messenger Express Customization Guide

Communications Services Documents

Use either one of the following URLs to see the documentation that applies to all Communications Services 6.2 2005Q1 products:

http://docs.sun.com/coll/MessagingServer_05q1

or

http://docs.sun.com/coll/CalendarServer_05q1

The following documents are available:

Sun Java System Communications Services Delegated Administrator Guide
Sun Java System Communications Services Schema Reference
Sun Java System Communications Services Event Notification Service Guide
Sun Java System Communications Express Administration Guide
Sun Java System Communications Express Customization Guide

---

Communications Express

These Release Notes contain important information available at the time of release of Sun Java™ System Communications Express 6.2 2005Q1 for HP-UX. New features and enhancements, known issues and limitations, and other information are addressed here.

This release notes contains the following sections:

About Communications Express 6.2 2005Q1
Communications Express Supported Browsers
Communications Express Installation Notes

About Communications Express 6.2 2005Q1

Sun Java™ System Communications Express Version 6.2 2005Q1 provides an integrated web-based communication and collaboration client that consists of three client modules - Calendar, Address Book and Mail. The Calendar and Address Book client modules are deployed as a single application on any web container and are collectively referred as the Unified Web Client (UWC). Messenger Express is the standalone web interface mail application that uses the HTTP service of the Messaging Server.

Communications Express Supported Browsers

Communications Express can be viewed using:

Netscape™ Communicator 6.2.x, 7
Internet Explorer™ 5.5 or higher
Mozilla™ 1.0 or higher

Communications Express Installation Notes

The following are the dependent services for Communications Express:

Directory Server. Install Sun Java™ System Directory Server version 5.2.
Calendar Server. Install Sun Java™ System Calendar Server Version 6.1.
Web Server. Install Sun Java™ System Web Server version 6.1 SP4 with JDK version1.5.
Messaging Server. Install Sun Java™ System Messaging Server 6.2.
Identity Server. Install Sun Java™ System Identity Server 6.2.
Application Server. Install Sun Java™ System Application Server 8.1.

Note	Communications Express has been tested and is supported only with the server versions mentioned above. The Communications Express for JES 3 Release can be deployed only on Sun Java System Application Server 8.1. The Communications Express configurator supports only the Domain Administration Server (DAS) deployment for Application Server 8.1.

Refer to chapter 2, “Installing and Configuring Communications Express” of Sun Java™ Systems Communications Express Administration Guide for instructions on how to install and configure Sun Java System Communications Express.

Refer to chapter 4, “Implementing Single Sign-On” of Sun Java™ Systems Communications Express Administration Guide for instructions on how to configure Sun Java System Communications Express when Identity Server is deployed.

---

Delegated Administrator Utility

These Release Notes contain important information available at the time of release of Sun Java™ System Delegated Administrator 6.2 2005Q1 for HP-UX. Known issues and limitations, and other information are addressed here.

This release notes contains the following sections:

About Delegated Administrator 6.2 2005Q1
Delegated Administrator Supported Browsers
Delegated Administrator Installation Notes

About Delegated Administrator 6.2 2005Q1

Sun Java™ System Delegated Administrator Version 6.2 2005Q1 is a set of command-line tools for provisioning users, groups, domains, and resources for Sun Java System Messaging Server and Sun Java System Calendar Server using Sun Java System Identity Server.

Delegated Administrator Supported Browsers

Delegated Administrator can be viewed using:

Netscape™ Communicator 6.2.x, 7
Internet Explorer™ 5.5 or higher
Mozilla™ 1.0 or higher

Delegated Administrator Installation Notes

The following are the dependent services for Delegated Administrator:

Directory Server. Install Sun Java™ System Directory Server version 5.2.
Calendar Server. Install Sun Java™ System Calendar Server Version 6.1.
Web Server. Install Sun Java™ System Web Server version 6.1 SP4 with JDK version1.5.
Messaging Server. Install Sun Java™ System Messaging Server 6.2.
Identity Server. Install Sun Java™ System Identity Server 6.2.
Application Server. Install Sun Java™ System Application Server 8.1.

Note	Delegated Administrator has been tested and is supported only with the server versions mentioned above. The Delegated Administrator for JES 3 Release can be deployed only on Sun Java System Application Server 8.1. Also, the Communication Express Configurator supports only the Domain Administration Server (DAS) deployment for Application Server 8.1.

---

Known Issues and Limitations

This section describes the known issues and limitations of Sun Java System Messaging Server 6.2 2005Q1 for HP-UX. For a list of the known issues and limitations in this component, refer to the following Release Notes:

http://docs.sun.com/app/docs/doc/819-0104

The following topics are the known issues:

Stopping Server

mmp server shows timeout when stopping the messaging server on HPUX (6276439).

The mmp server shows timeout before getting killed, when stopping the messaging server on HP-UX.

Workaround

None.

---

Redistributable Files

The following redistributable files are provided with Messaging Server 6.2:

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/

---

How to Report Problems and Provide Feedback

If you have problems with Sun Java System Messaging Server, contact Sun customer support using one of the following mechanisms:

Sun Software Support services online at
http://www.sun.com/service/sunone/software

This site has links to the Knowledge Base, Online Support Center, and ProductTracker, as well as to maintenance programs and support contact numbers.

The telephone dispatch number associated with your maintenance contract

So that we can best assist you in resolving problems, please have the following information available when you contact support:

Description of the problem, including the situation where the problem occurs and its impact on your operation
Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
Detailed steps on the methods you have used to reproduce the problem
Any error logs or core dumps

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions.

To share your comments, go to http://docs.sun.com and click Send Comments. In the online form, provide the document title and part number. The part number is a seven-digit or nine-digit number that can be found on the title page of the guide or at the top of the document.

---

Additional Sun Resources

Useful Sun Java System information can be found at the following Internet locations:

Documentation for Messaging Server
http://docs.sun.com/app/docs/coll/MessagingServer_05q1
Sun Java System Documentation
http://docs.sun.com/prod/java.sys
Sun Java System Professional Services
http://www.sun.com/service/sunps/sunone
Sun Java System Software Products and Service
http://www.sun.com/software
Sun Java System Software Support Services
http://www.sun.com/service/sunone/software
Sun Java System Support and Knowledge Base
http://www.sun.com/service/support/software
Sun Java System Software Support Services
http://www.sun.com/support/
Sun Java System Consulting and Professional Services
http://www.sun.com/service/sunps/sunone
Sun Java System Developer Information
http://developers.sun.com
Sun Developer Support Services
http://www.sun.com/developers/support
Sun Java System Software Training
http://www.sun.com/software/training
Sun Software Data Sheets
http://wwws.sun.com/software

---

Copyright � 2005 Sun Microsystems, Inc. All rights reserved.

Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.

SUN PROPRIETARY/CONFIDENTIAL.

U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.

Use is subject to license terms.

This distribution may include materials developed by third parties.

Portions may be derived from Berkeley BSD systems, licensed from U. of CA.

This product includes software developed by Computing Services at Carnegie Mellon University (http://www.cmu.edu/computing/).

Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.

---

Copyright � 2005 Sun Microsystems, Inc. Tous droits r�serv�s.

Sun Microsystems, Inc. d�tient les droits de propri�t� intellectuels relatifs � la technologie incorpor�e dans le produit qui est d�crit dans ce document. En particulier, et ce sans limitation, ces droits de propri�t� intellectuelle peuvent inclure un ou plusieurs des brevets am�ricains list�s � l'adresse http://www.sun.com/patents et et un ou des brevets des applications de brevet en attente aux Etats - Unis et dans les autres pays.

Propri�t� de SUN/CONFIDENTIEL.

L'utilisation est soumise aux termes du contrat de licence.

Cette distribution peut comprendre des composants d�velopp�s par des tierces parties.

Des parties de ce produit pourront �tre d�riv�es des syst�mes Berkeley BSD licenci�s par l'Universit� de Californie.

Ce produit comprend du logiciel d�velop� par Computing Services � Carnegie Mellon University (http://www.cmu.edu/computing/).

Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques d�pos�es de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.

Toutes les marques SPARC sont utilis�es sous licence et sont des marques de fabrique ou des marques d�pos�es de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.