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

Version 6.2 2005Q4

Part Number 819-4255-10

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

The most up-to-date version of these release notes can be found at the Sun Java System documentation web site: http://docs.sun.com/app/docs/prod/entsys.05q4. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and product documentation.

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

Messaging Server
Delegated Administrator

These release notes contain the following sections:

Release Notes Revision History
About Messaging Server 6.2 2005Q4
Bugs Fixed in This Release
Important Information
Delegated Administrator
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 2006	Revenue release.
November 2005	Beta release.

---

About Messaging Server 6.2 2005Q4

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 2005Q4 release:

Communications Server Delegated Administrator is the recommended mechanism for provisioning Messaging Server and Sun Java System Calendar Server (Calendar Server) users. For more information, see Delegated Administrator.
The Access Manager (formerly called Identity Server) Services provide Messaging and Calendar Server LDAP user entry provisioning. The Access Manager Services interface now allows input validation. See http://docs.sun.com/app/docs/coll/1292.1 for more information.
New MTA Features

The type of transport protocol in use (SMTP/ESMTP/LMTP) is now logged and made available to the various access mappings. Two new modifier characters have been added to the set that can appear after an action indicator in the mail.log* files:

E - An EHLO command was issued/accepted and therefore ESMTP was used

L - LMTP was used

Previously, the only modifier characters that would appears were A (SASL authentication used) and S (TLS/SSL used). Additionally, the $E and $L flags respectively will be set as appropriate for the various *_ACCESS mappings.

Wildcards are now allowed in the strings used to match verdicts returned by spam filters. imsimta encode now supports three new switches:

-disposition=VALUE Sets the content-disposition to the specified VALUE

-parameters=NAME=VALUE Specifies one or more additional content-type parameters and their values -dparameters=NAME=VALUE Specifies one or more additional content-disposition parameters and their values

Bit 4 (value 16) of the DOMAIN_UPLEVEL MTA option is now used to control whether address reversal rewriting is:

Skipped if the address is a mailEquivalentAddress (bit clear)
Performed only if the address is a mailAlternateAddress (bit set)

A value (/) given as an [envelope_from] nonpositional alias parameter, as an errors to positional alias parameter, or as a value of the mgrpErrorsTo LDAP attribute is now interpreted as a request to revert to using the original envelope from address for the incoming message while retaining mailing list semantics. This can be useful for setting up mailing lists that report all forms of list errors to the original sender.

The Job Controller directory sweep has been updated. Instead of reading all the files in the queue directory in the order in which they are found, it reads several channel queue directories at once. This makes for much more reasonable behavior on startup, restart, and after max_messages has been exceeded. The number of directories to be read at once is controlled by the Job Controller option Rebuild_Parallel_Channel. This can take any value between 1 and 100. The default is 12.

The sieve interpreter now keeps track of whether a response message was generated by a notify or vacation action and logs this information as needed.

The option Rebuild_In_Order parameter has been added to the job_controller. If this is set to a non-zero value, then on startup, the Job Controller adds previously untried (ZZ*) messages to the delivery queue in creation order. Previous (and default) behavior is to add the messages in the order in which they are found on disk. There is a cost associated with recreating the queues in order.

Some additional reasons why a requested vacation response isn’t sent are now logged.

Messaging Server has introduced additional features and updates that will be described in forthcoming Beta refresh release notes.

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.

The following bugs affect the deprecated Messenger Express product:

The Up and Down buttons removed (no bugid)

The Up and Down buttons used to specify the ordering of your filters have been removed.

Buildhash directories should not be referenced in the Messenger Express Customization Guide (6190726)

The documentation should have referenced the ispell source files available at: http://www.gnu.org/software/ispell/ispell.html.

Problems may be seen in Messenger Express on Internet Explorer 6 when proxy server setting is used (4925995)

Workaround

Enable or disable “auto-detection” option in Internet Explorer’s encoding menu. Use direct connection or switch to different proxy server.

Feature removed from the Advanced Mail Filter Conditions window (4908625)

The ability to specify a time frame for your filters has been removed from the Advanced Mail Filter Conditions window (of the Mail Filters user interface) for the Messaging Server 6.0 Patch 1 release. The feature was removed because the underlying support is not available.

If you create groups within an existing group, you may encounter the following error: pab:PAB_ModifyAttribute: ldap error (No Such object) (4883651)

Localized Messenger Express does not merge some of the folders created by Outlook Express (4653960)

It is sometimes desired that default “Sent” folder in Messenger Express can be replaced with “Sent Items” folder created by Outlook Express, hence all the messages sent by both client is copied to “Sent Items” folder. This operation is difficult, particularly in Japanese.

Workaround

Edit Japanese i18n.js to match Outlook Express’ “Sent Items” translation

i18n[’sent folder IE’] = ’soushinzumiaitemu’

fldr[’Sent Items’] = ’soushinzumiaitemu’

End users must log onto Messaging Server using Outlook Express first.

With Directory Server 5.1 or later, you will not be able to enter multiple email IDs for a single contact in the Personal Address Book (4633171)

Note that Directory Server is exhibiting correct behavior. Due to a problem in Netscape Directory Server 4.x, you are able to enter multiple email IDs.

Administration Console

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

The following bugs affect the deprecated Administration Console product:

Administration Console can not be started on Red Hat Linux platforms (6215646)

On Red Hat Linux 3.x, Administration console can not be started. If you click Messaging Server node or Open button on Administration Console, nothing happens. On Red Hat Linux 2.x, Console is started but is missing Manage Certificate button.

Can’t start/stop services from Administration console (6215105)

Can’t stop IMAP, POP, MTA and HTTP services from Administration console; eventually, the console freezes. This bug will be fixed in the forthcoming patch release.

Administration Server console does not recognize preconfigured Messaging Server in SSL mode (5085667)

If you have preconfigured the Messaging Server for SSL use, and if you access the Messaging Server configuration from the Administration Server console, the console does not recognize the installed certificates. The Administration Server console attempts to create a new key database.

Workaround

Before you use the Administration Console, create symbolic links (symlinks) for the SSL certificates from the <msg-svr-root \>/config area to the <admin-server-root\>/alias area, as follows:

From <msg-svr-root \>/config/cert8.db (or cert7.db) to

<admin-server-root \>/alias/msg-config-cert8.db (or cert7.db)

From <msg-svr-root \>/config/key3.db to <admin-server-root\>/alias/msg-config-key3.db

(Linux) Messaging Server console shows an error opening online help (5054732)

Cannot Create a User Through the Administration Console (4852026 & 4852004)

Messaging Server no longer supports user or group creation using the Administration Console. User and group entries should be created using the User Management Utilities. The following error messages may appear when logging in as, or sending mail to, a user created using Administration Console:

Quota root does not exist

4.0.0 temporary error returned by alias expansion: . . .

Netscape Browser Support

Firefox browser support will replace Netscape browser support at a future date.

The Communications Services 6 2005Q4 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 2005Q4 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 2005Q4 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.q

ueuedir 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/app/docs/doc/819-2328) 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/app/docs/doc/819-2328).

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/app/docs/doc/819-2328).

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 2005Q4 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 Application Server	7.x and 8.x
Sun Java System Web Server	6.1 (with iPlanet™ Delegated Administrator)

NSS Version Requirements

Messaging Server 6.2 2005Q4 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/app/docs/doc/819-2328) and
Sun Java Enterprise System Release Notes (http://docs.sun.com/app/docs/doc/819-1570).

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/app/docs/doc/819-2650 for more information on autoreply). In addition, NFS can be supported on BSD-style mailboxes (/var/mail/).

---

Bugs Fixed in This Release

This section describes the bugs fixed in the Messaging Server 6 2005Q4 release that were documented as known issues in previous Messaging Server Release Notes.

For a complete list of bugs fixed in this release, see the README file delivered with the Messaging Server core software patch.

Table 5  Fixed Bugs in Messaging Server 6.2 2005Q4

4962377	A log records now include authorization information
4974428	Packages have a default BASEDIR of /opt
4985907	Corrupt Japanese Delivery Reports
4987384	SunONE_MsgSvr script echoes unnecessary -n
5048159	STATUS command is slow on large fragmented mailbox
5060638	French localization: &_agrave; instead accented a in “Mettre a jour” label
5064300	Need configuration option to limit number of folders /sub-folders
5091535	XFILE: 5090205, tcp_smtp_server dumps core with LDAP over SSL
5098299	Notification failure error in amSession log during logging out from Communications Express
5100202	Add addresses: does not add all entries into the Personal Address Book
5104279	Return job doesn’t recognize messages with urgent priority
5106562	Illegal commands can cause imsimta qm to dump core
6183650	tcp_smtp_server performance problem (100% CPU utilization)
6184095	Upgrade script should deprecate autoreply channel
6186334	S/MIME: retry on WMAP commands when HTTP connection lost inApplet
6191074	Request limitation on physical number of messages per folder and logmessage
6196349	Console hangs when setting expire rule with header constraints
6196879	Include user original over the wire login ID in MMP log output
6198129	Quota bar is not right when user is over quota
6199242	Accented messages are not being displayed correctly
6200132	SMIME message not sent with priority requested
6200692	RENAME operation from a personal folder to a shared folder succeeds but
6202176	imsbackup does not backup user defined flags
6203551	System flags are not restored when restoring form SPARC to x86
6204204	Add -i option to imsimport to ignore Content-Length
6204294	Click on shared folder, then click on INBOX get JavaScript error
6204409	Setting mail forwarding is possible without entering a mail forwarding address
6204911	msprobe logs messages to the imta log file
6205866	imsimport is not checking the two leading new lines in From_ line
6205957	service.readtimeout should be set to 30 by default
6206104	need reconstruct (or some tool) to correct bad store.sub
6206193	Multiple packages deliver the same binary for SUNWmsgwm and SUNWmsges
6207499	Cannot break the mboxutil -o command
6207512	imsrestore restores the INBOX on second attempt when threshold is exceeded
6207518	mboxutil -d returns Unknown code __9F 242
6207865	stored time out waiting for processes to exit must be finite
6209210	immonitor-access appears to calculate IMAP time incorrectly, when combined with SMTP
6209318	SNMP sub agent fails to come up.
6211683	Going out from mail tab to other tab causes folder tree to disappear
6211969	Possible memory corruption when sleepycat transaction fails
6212021	reconstruct -m reports fixing quotas, but doesn’t
6212408	Memory leaks when opening a corrupted mailbox
6212524	Memory leaks in reconstruct when mailbox is corrupted
6213176	Utilities should tell the user as well as log that the watcher is not running
6214039	spamfilterXoptin broken
6214056	Encode unparseable address header fields
6214098	Fix mboxutil usage: duplicate entry for -d option, -P not listed as valid parameters to -d
6214559	Unread message count disappears when user clicks on View Message Header Detail
6214941	imsconnutil -c logs store emergency error when there is no connected user
6215105	Can’t start/stop services (IMAP/POP/MTA/HTTP) from Messaging Server console.
6215535	Expired encrypting certificate causes valid signature displayed as invalid when viewed by recipient
6215928	Encode 8 bits header (sender)
6216924	start-msg creates error message while testing on NFS
6217848	ims_master dumped core when mailmessagestore LDAP attribute is invalid
6218016	RFE: Generate a log message automatically when MAX_MESSAGES is exceeded
6218085	Mailbox corruption reported when none exists
6219856	5.2P2 to 6.2 upgrade: primary partition path is not modified
6219866	Upgrade from 5.2P2 to 6.2: make_mta_config_changes.sh fails on certain copy commands
6220293	Perform job controller rebuild in such a way that the startup is more fair
6221332	Change ICAP request string to avoid 201 response
6221409	Spamfilter support enhancements for new version of Brightmail
6221971	Unable to make a fresh restart of messaging services via administration console after changes
6222031	Setting URL_RESULT_CACHE_SIZE to 0 breaks URL result processing
6222639	Bookkeeping error counting delayed messages
6222841	HTTP daemon crashes on deleting folder after creating a subfolder
6223834	immonitor-access -I core dumps when user in hosted domain
6223848	reconstruct does not notice all nulls in cache record
6225212	Administration Console invoked in German sets expire rule with German for or
6225252	imsimport creates mailbox with uppercase domain name
6225506	Customer wants to use $subject in his autoreply message
6225708	Reconstruct core on Ctrl/C with iBiff
6225730	Case sensitive causes problems with reconstruct
6226020	imsimta encode -header -filename with multiple files botches boundary marker
6226161	Version of comm_dssetup.pl in /opt/SUNWmsgsr/install corrupts Access Manager
6226915	$N with no argument in AUTH_REWRITE doesn’t get default error text
6227966	Cannot break (Ctrl-C) the msuserpurge command
6228002	imsched dumped core during refresh
6228422	AService program core dump when configuration file permissions incorrect
6229781	Audit access control changes on IMAP folders
6230704	SNMP shows 0 values for all message access information
6231048	job_controller looping in addtopriorityqueue (ETRN)
6231202	Garbage in Y records in log files
6231361	problems setting large quotas on a user basis
6231733	Use heuristic parse to extract address from headers for AUTH_REWRITE
6231993	messages will not be dequeued from defragment channel
6232090	probe test fails to restart dispatcher daemon after dispatcher daemon is killed
6232268	MTA passes “” as the quota value to the store when quota information is not available
6232311	transactionlimit keyword not working
6232802	disconnecttransactionlimit not getting checked at MAIL FROM stage
6233449	Regression: tcp_smtp_server and imap both dumped core XFILE 6235303
6233479	MMP needs ability to change user search filter within domain when inetDomainSearchFilter is not set
6234542	Copying a large message to a folder on another server fails
6234674	String concatenate doesn’t guard against append argument being too long
6234695	Spamfilter error handling calls wrong routine
6235058	iminitquota should check and repair overquota mailuserstatus when overquotastatus is enabled
6235382	Setting local.store.overquotastatus town’ does not enable quota overdraft mode automatically
6236243	Clean up sieve setdate support
6236245	Add support to sieve notify to include original message in new message
6237533	mboxutil -o does not list orphan mailboxes that have LDAP entries with different case in the UIDs
6238652	Invalid ’Mailbox corrupted, appears truncated’ error from ims_master
6239259	Incorrect message size logged by MTA if message submission is rejected
6239614	Missing leading new line in a From line of an exported mailbox
6239755	More log info when SMTP connection aborted
6240741	Folders to be managed only by privileged accounts with proper ACL semantic
6240796	ims_master should defer additional recipients when it detects shutdown time out
6242994	imexpire command doesn’t terminate fast enough
6243696	Too many msprobe processes hanging around when there is database hang/lock
6243967	dbhang/deadlock after running stress for 45 minutes
6244028	msprobe not recognizing SSL-only MMP configuration
6244207	msprobe need to be able to test SSL ports
6244671	Regression: spaces in certmap.conf issuerDN cause parsing error
6244723	imsbackup hangs on some Windows folders.
6244775	Administration Server: Incorrectly built binary which accesses errno or h_errno directly
6244856	Should sanity check service.http.idletimeout
6245470	mboxutil operations should log input from -f file
6246028	job_controller core null message removefrompriorityqueue after reload
6246247	SMS channel may core in header processing (he_) routines
6247383	imsexport produces invalid date format in From line
6247677	Log Message in imsbackup should indicate which file is problematic
6249578	Logging RFE: Failed index file open/read message needs more information.
6250671	Messenger Express Multiplexor: user is redirected to the login page if the session ID contains a ’+’ or a ’/’
6251752	mshttpd core dump in saslglue_conn_new ()
6251852	Messages still send to the store after message store disk availability check enabled
6252960	Off by one error in check of ALLOW_TRANSACTIONS_PER_SESSION option
6253743	sslconnect dumps core
6255339	Return job not passing envelope from address to notification generator
6255489	Cannot create a sub folder in a shared folder from another user in a non default domain
6259539	MTA SDK may core (SEGV) when dequeueing a message with multiple recipients
6259896	MTA SDK envelope recipient address lookup failures
6260796	imsimta clbuild fails during postpatch
6261048	Out of box installation should not enable SSL
6261136	Messages are still appended onto Sent folder via Communications Express even if one is over quota
6261566	Multiple notifications are being sent for delayed messages
6261852	start-msg not detecting the presence of SNMP sub-agent
6262295	MTA SDK may report inapt and confusing error codes
6262675	Unexpected outstanding SSL handshake message log level needs to be adjusted
6263895	Result of PERSONAL_NAMES mapping and LDAP_PERSONAL_NAMES should be automatically quoted if necessary
6264192	Need ability to start SMPP PDU sequence numbers at a value other than 0x00000000
6264200	Wrong message sent when delivering via LMTP and NOTIFY=SUCCESS set
6264543	Messaging Server patch needs to be patch automation friendly
6264566	Request for more detailed logging of MMP operations
6265235	Trusted circle SSO fails when inetDomainSearchFilter is configured in Messaging Server
6265361	Incorrect pthread_cond_timedwait() call may lead to undefined behavior in SMS channel, MTA SDK
6265442	Different behavior of imsimta process command on Linux platform
6266169	configmsg_init_default() only loads configuration once
6267592	iminitquota should issue right error message instead of “Unknown code __9F 242”
6268197	Running stored from a directory not readable by mailsrv user can cause database log accumulation error
6268200	imsrestore -n does not work
6268438	Messages appearing in MTA debug logs without master_debug keyword specified
6268969	Vacation messages are sent with a spurious line break every 1024 characters
6269089	History line written when LMPT encounters all address ugly condition is incomplete
6271555	Typography mistake in ULA database:’signing cert’ instead of’signing certificate
6272281	readership command fails with a folder in Japanese characters
6273362	Inner forcing text mode processing of text mime types
6274098	mshttpd cores - free calls abort in dm_dispose_result after fix for bug 6269460
6274165	Job Controller client API does not correctly handle read errors
6274166	Job Controller can hang in readline() when transmitted data contains a NUL
6274342	MMP logfiles become unreadable due to missing CR
6275540	msprobe reporting Unable to open AService.cfg

---

Important Information

This section covers the following topics:

Installation Notes
Compatibility Issues
Documentation Details for Messaging Server 6.2 2005Q4
Accessibility Features for People With Disabilities

Installation Notes

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

Installation Overview for Messaging Server

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

For installation instructions, see the Sun Java Enterprise System 2005Q4 Installation Guide
(http://docs.sun.com/app/docs/doc/819-2328).

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 2005Q4 Administration Guide (http://docs.sun.com/app/docs/doc/819-2650).

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 2005Q4 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 2005Q4 Installation Guide
(http://docs.sun.com/app/docs/doc/819-2328).

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.

Patch Requirement Information

The following table gives the numbers and minimum versions for the alignment patches. All patches referred to in this section are the minimum version number required for upgrade. It is possible that a new version of the patch has been issued since this document was published. A newer version is indicated by a different version number at the end of the patch. For example: 123456-04 is a newer version of 123456-02 but they are the same patch ID. Refer to the README file for each patch listed for special instructions.

To access the patches, go to http://sunsolve.sun.com.

Table 6  Messaging Server 6 2005Q4 Alignment Patches Required for HP-UX

Patch Number	Patch Description
121393-01	HP-UX 11.11: Sun Java™ System Directory Server 5 2005Q4
121931-01	HP-UX 11.11: Sun Java™ System Directory Server 5 2005Q4 (Localization Patch)
121513-01	HP-UX 11.11: Directory Preparation Tool
121511-01	HP-UX 11.11: Sun Java™ System Messaging Server 6 2005Q4
121927-01	HP-UX 11.11: Sun Java™ System Messaging Server 6 2005Q4 (Localization Patch)
121515-01	HP-UX 11.11: Sun Java™ System Administration Server 6 2005Q4
121933-01	HP-UX 11.11: Sun Java™ System Administration Server 6 2005Q4 (Localization Patch)

For detailed information about Upgrade procedure of the Messaging Server from JES3 to JES4 refer Sun Java Enterprise System 2005Q4 Upgrade Guide for HP-UX located at http://docs.sun.com/app/docs/doc/819-4460.

Compatibility Issues

The following are the compatibility issues with Messaging Server:

Access Manager now has two installation types: Enhanced and Compatible.

At installation, you must choose Compatible as the install type on the following panel:

Access Manager: Administration (1 of 6)

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.

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

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.

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

These Release Notes are the only document published with the Delegated Administrator Utility 6.2 2005Q4 on HP-UX platform. Use the following URL to see all the Messaging Server 6.2 2005 Q4 documentation:

http://docs.sun.com/app/docs/coll/1312.1.

Messaging Server 6.2 2005Q4 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 2005Q4 products:

http://docs.sun.com/app/docs/coll/1312.1.

or

http://docs.sun.com/app/docs/coll/1313.1.

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

Accessibility Features for People With Disabilities

To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at http://sun.com/software/javaenterprisesystem/get.html.

For information on Sun’s commitment to accessibility, visit http://sun.com/access.

---

Known Issues and Limitations

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

The following are the product areas covered:

Installation, Upgrade, and Uninstallation
Stress Test
Messaging Server
Localization
Documentation Details for Messaging Server 6.2 2005Q4

Installation, Upgrade, and Uninstallation

This section describes known issues with installing, upgrading, and uninstalling of Messaging Server.

Stress Test

Connection Timeout errors during load conditions

Workaround

Change the kernel parameter value of nfile to maximum using SAM
The tcp_time_wait_interval should be reduced from 60000 to 30000 using the following command.

ndd -set /dev/tcp tcp_time_wait_interval 30000

Set the number of threads for each of the services to 25 using

Configutil –o service.http.maxthreads –v 25

Configutil –o service.pop.maxthreads –v 25

Configutil –o service.imap.maxthreads –v 25

Messaging Server

This section describes known issues in the Messaging Server product.

Messaging server start up script is hanging (6369071)

Store server takes some time to comeup, hence wait for a while after giving start-msg command.

Sending and Receiving mail through the Messaging Server will not work if sendmail is running. The Sendmail service running on HP-UX stops the Messaging Server service (no bugid)

Workaround: Kill the sendmail service and start the Messaging Server.

In option.dat, lines starting with #, !, or ; symbols are treated as comment lines (no bugid)

In option.dat files, Messaging Server treats lines beginning with pound sign (#), exclamation point (!), or semicolon (;) characters as comment lines— even if the preceding line has a trailing backslash (\\), which means the line is being continued. Consequently, you must be careful when working with long options (particularly delivery options) containing these characters.

There is a workaround for delivery options in which a natural layout could lead to continuation lines starting with a # or !.

Workaround

In delivery options, Messaging Server ignores spaces following the commas that separate individual delivery option types.

For example, instead of:

DELIVERY_OPTIONS=\\

#*mailbox=@$X.LMTP:$M$_+$2S%$\\$2I@ims_daemon,\\

#&members=*,\\

*native=@$X.lmtpnative:$M,\\

*unix=@$X.lmtpnative:$M,\\

/hold=$L%$D@hold,\\

*file=@$X.lmtpnative:+$F,\\

&@members_offline=*,\\

program=$M%$P@pipe-daemon,\\

forward=**,\\

*^!autoreply=$M+$D@bitbucket

You can workaround the problem by adding spaces as follows:

DELIVERY_OPTIONS=\\

#*mailbox=@$X.LMTP:$M$_+$2S%$\\$2I@ims_daemon,\\

#&members=*,\\

#*native=@$X.lmtpnative:$M,\\

#*unix=@$X.lmtpnative:$M,\\

#/hold=$L%$D@hold,\\

#*file=@$X.lmtpnative:+$F,\\

#&@members_offline=*,\\

#program=$M%$P@pipe-daemon,\\

#forward=**,\\

#*^!autoreply=$M+$D@bitbucket

DOMAIN_UPLEVEL has been modified (no bugid)

The DOMAIN_UPLEVEL default value has changed from 1 to 0.

The following characters cannot be used in the User ID: $ ~ = # * + % ! @ , { } ( ) / < \> ; : " ” [ ] & ? (no bugid)

This constraint is enforced by MTA when operating in direct LDAP mode. Allowing these characters in the User ID can cause problems in the message store. If you want to change the list of characters forbidden by the MTA, set the following option by listing a comma-separated string of the characters’ ASCII values:

LDAP_UID_INVALID_CHARS=32,33,34,35,36,37,38,40,41,42,43,44,47,58,59,60,61,62,

in the /opt/sun/messaging/config/options.dat file. Note that you are strongly advised against relaxing this constraint.

The destinationspamfilter<>X optin channel keyword doesn’t work (6214039)

This keyword will be fixed in the upcoming Messaging Server patch release.

NSS errors in the imta logfile when SSL is not configured (6200993)

These are not harmful errors. They are caused by the system’s inability to find SSL certificates in the SSL configuration.

Workaround

You can disable SSL in the MTA as well as the Message Store:

Edit imta.cnf file and remove the channel keyword maytlsserver from tcp_local and tcp_intranet channels.
Change the following configutil configuration parameters by setting service.imap.sslusessl to ’no’ and service.pop.sslusessl to ’no’.
Recompile the MTA configuration with the imsimta cnbuild command.
Restart the services (stop-msg/start-msg). This will disable the support for SSL. Please make sure that, once you need to configure the server in SSL mode after having certificates, you need to revert back the changes you have made for it.

Cannot log in to Messaging Server from Internet Explorer 6.0 SP1 when using a proxy server (5043607)

When using an HTTP proxy in IE 6.0 SP1 on a PC as a client, you may experience difficulty in logging into Messaging Server. This problem is likely to be due to a non-standard compliant proxy server and cannot be fixed in Messaging Server.

Correct certmap.conf file content required for client certificate authentication (496734)

The certmap.conf configuration file specifies how to map a certificate to an entry in the LDAP directory. By default, the certificate subject (with two lines commented out) contains the exact DN of the LDAP directory entry.

However, a very common alternative behavior is to extract a particular attribute from the subject of the certificate and to search the directory for that attribute.

Workaround

To achieve this alternative behavior, change:

certmap default default

#default:DNComps

#default:FilterComps e, uid

to:

certmap default default

default:DNComps

default:FilterComps e

For a complete description of certmap.conf, please refer to the Sun Java System Server Console 5.2 Server Management Guide.

Will not see channel is stopped if jobc was recently started (4965338)

In Messaging Server 5.2, if you issued a #imsimta qm summarize command you could view the channels that had been stopped with the imsimta qm stop <chan\> command.

This behavior changed in 6.0. If you have not used a channel yet, you will not get the 0 lines and you will not see the stopped channels.

Manage Certificate wizard not creating Secure Sockets Layer (SSL) certificates under Messaging Server/Configuration (4939810)

When you use the Manage Certificate option (Administration Server-\>Messaging Server-\>Configuration-\>Manage Certificate) to create an SSL certificate request, the Manage Certificate wizard should create a certificate and key database in the Messaging_Server_Base/config area and not in the Admin_Server_Root/alias area. In addition, the file prefixes should change from the msg-config value (msg-config-cert7.db and msg-config-key3.db) to NULL (cert7.db and key3.db).

Workaround

Copy the msg-config-cert7.db and msg-config-key3.db files from Admin_Server_Base/alias area to Messaging_Server_Base/config area as cert7.db and key3.db with proper permissions and ownerships.
Create soft links for the files under Messaging_Server_Base/config area with the proper permissions and ownerships used in the Admin_Server_Base/alias area.

imsimta start doesn’t start disp and job controller (4916996)

The imsimta start, imsimta restart, and imsimta refresh commands work only when the watcher process is running.

Note	New start-msg and stop-msg commands have replaced imsimta start and imsimta stop, which are deprecated and will be removed in a future release. For more information about the start-msg and stop-msg commands, refer to the Messaging Server Administration Guide.

The XSTA, XADR commands are enabled by default (4910371)

After installation, the SMTP extension commands XSTA and XADR are enabled by default, which may enable remote and local users to retrieve sensitive information.

Workaround

Add the following lines to the imta/config/tcp_local_options file (create this file if necessary) to disable the XSTA and XADR commands:

DISABLE_ADDRESS=1

DISABLE_CIRCUIT=1

DISABLE_STATUS=1

DISABLE_GENERAL=1

Searching for a home phone number does not work in the Personal Address Book (4877800)

A Personal Address Book search based on “Phone #” searches for the work phone number attribute only. You cannot use “Phone #” to search for home or mobile phone numbers.

If indirect dependencies already exist between Sun Cluster resources, scds_hasp_check() may prevent HAStoragePlus from being supported with those existing configurations (4827911)

This behavior is observed in Sun Cluster 3.0 Update 3.

Workaround

Create a weak dependency for the existing resources on the HAStoragePlus resource.

Messenger Express Multiplexor (MEM) does no have a configuration option to make use of the OS resolver or NSCD (4823042)

Workaround

Configure system as a caching-only DNS server in order to gain the benefit of caching MX and A records.

MoveUser utility does not work on a mailbox that contains over 1024 subfolders (4737262)

It has been reported that the MoveUser utility stops when attempting to move a

user’s account that has a mailbox containing over 1024 subfolders.

Access control filters do not work if the short form domain in used in the /etc/hosts file (4629001)

If there is a short form version of a domain name in the /etc/hosts file, there will be problems if you use a host name in an access control filter. When the IP address lookup returns a short form version of the domain name, the match will fail. Therefore, you should make sure you use a fully qualified domain name in the /etc/hosts file.

To take effect, changes made using configutil often require a restart of the affected server or servers. (4538366)

Administration Server access control host names are case-sensitive (4541448)

When you configure “Host Names to allow” for the Administration Server, the access control list is case-sensitive. If the DNS server uses mixed-case host names in the IN-ADDR records (used when translating from an IP address to a domain name), the access control list must use the same case. For example, if your host is test.Sesta.Com, then the access control list must include *.Sesta.Com. Due to this problem, *.sesta.com will not suffice.

For example, if the user/group base suffix is o=isp, then the DN of the service administrator group is cn=Service Administrators, ou=groups, o=isp . To designate the account uid=ofanning, o=sesta.com, o=isp as a service administrator, you should add the account’s DN to the group. In the following modify record, the designated user is added as a group member in the LDIF:

dn: cn=Service Administrators,ou=groups,o=isp changetype: modify add: uniquemember uniquemem

Furthermore, for users to have service administrator privileges, the attribute memberof must be added to the user entry and set to the Service Administrator Group, for example:

dn: uid=ofanning, o=sesta.com, o=isp

changetype: modify

add: memberof

memberof: cn=Service Administrators, ou=groups, o=isp

The MMP BadGuy configuration parameter, BGExcluded, does not work (4538273)

Workaround

Deploy separate MMP servers to handle the clients that are excluded from bad guy

rules. These servers must have BadGuy turned off.

LDAP search performance is slightly impacted by ACIs in Directory Server version 5.x (4534356)

This issue affects many searches performed by Messaging Server. For faster searches, use directory manager credentials with the following commands to access the directory:

/opt/sun/messaging/sbin/configutil -o local.ugldapbinddn -v “rootdn” -l

/opt/sun/messaging/sbin/configutil -o local.ugldapbindcred -v “rootdn_passwd” -l

where rootdn and rootdn_passwd are the credentials of Directory Server’s administrator.

If you enable Sun Cluster 3.0 Update 3, you may encounter a harmless error message (4490877)

The following harmless error message appears in the Sun Cluster console and also in /var/adm/messages, when starting High Availability (HA) services or when switching HA services from one node to another:

Cluster.PMF.pmfd: Error opening procfs control file

</proc/20700/ctl\> for tag <falcon,habanero_msg,4.svc\>: No such

file or directory

Localization

The following known issues are not necessarily localization-specific issues.

Administration Console is unable to start in German, Spanish, Simplified Chinese, and Traditional Chinese locales (6270696)

Workaround

Create the symbolic link manually:

ln -s /opt/sun/messaging/lib/jars/msgadmin62-2_06_lang.jar

AdminServer_ServerRoot/java/jars/msgadmin62-2_06_lang.jar

On Solaris (SPARC and x86 platforms), you also need to create the correct version .jar files manually:

cp /opt/sun/messaging/lib/jars/msgadmin62-2_03_lang.jar

/opt/sun/messaging/lib/jars/msgadmin62-2_06_lang.jar

Accents are poorly encoded in Messenger Express messages on Internet Explorer browsers (6268609)

This problem is not seen in Communications Express messages.

Configurator input field is too narrow to view (6192725)

Some input fields in the Messaging Server configurator (invoked by msg_svr_root/sbin/configure) are too narrow to see on some pages in non-English locales on Linux platforms.

Configurator input field is too narrow to view (6192725)

Workaround

Widen the window size to make input field larger enough to view.

(German) Group in address book cannot be created. (5044669)

Workaround

In var/opt/sun/messaging/config/html/de/editPabGroup_fs.html, change:

...der folgenden Optionen, um fortzufahren, oder klicken Sie auf

\qAbbrechen\q

to

...der folgenden Optionen, um fortzufahren, oder klicken Sie auf

\\\qAbbrechen\\\q

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:
/opt/sun/messaging/config/html (and subdirectories)
/opt/sun/messaging/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:
/opt/sun/messaging/examples/meauthsdk/expapi.h
/opt/sun/messaging/examples/tpauthsdk/authserv.h
All files in the /opt/sun/messaging/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:
/opt/sun/messaging/examples/meauthsdk/examples/meauthsdk/
/opt/sun/messaging/examples/tpauthsdk/
/opt/sun/messaging/examples/mtasdk/

---

Delegated Administrator

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

This release notes contains the following sections:

About Delegated Administrator 6.3 2005Q4
What’s New in Delegated Administrator 6.3 2005Q4
Delegated Administrator Supported Browsers
Bugs Fixed in This Release
Java Enterprise System Components
Deployment Guidelines
Hardware Requirements
Browsers
Delegated Administrator Known Issues and Limitations
Delegated Administrator Installation Notes

About Delegated Administrator 6.3 2005Q4

Sun Java System Communications Services Delegated Administrator enables you to provision organizations (domains), users, groups, and resources in an LDAP directory used by Communications Services applications such as Messaging Server and Calendar Server.

The Delegated Administrator tool has two interfaces:

A utility (a set of command-line tools) invoked with the commadmin command.
A console (a graphical user interface) accessible through a Web browser.

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, and for a description of the commadmin command-line tools, see the Sun Java System Communications Services 6 2005Q4 Delegated Administrator Guide.

What’s New in Delegated Administrator 6.3 2005Q4

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.

The Delegated Administrator 6.3 2005Q4 release implements the following new features:

The Delegated Administrator console’s interface has been improved. For example, the following enhancements have been made:
In the organization view, a second row of tabs has been added. By selecting these tabs, you can display lists of users, groups, Calendar resources, service packages, or properties.
The Users list in an organization now displays each user’s email address, mailbox status, and the service package(s) assigned to each user.

The Delegated Administrator console supports Calendar Server.

In earlier releases, only the Delegated Administrator utility (commadmin) supported Calendar Server.

The following bullet items list the console features that implement support for Calendar Server:

The Calendar service can be added to organizations, users, and groups.
You can create and manage groups in the console. Groups can have mail service (mailing lists), required to support Calendar Server.
You can create and manage Calendar resources in the console.
Service packages can now include Calendar service.

Bugs Fixed in This Release

The table below describes the bugs fixed in Delegated Administrator 6.3 2005Q4.

Table 7  Fixed Bugs in Delegated Administrator 6.3 2005Q4

Bug Number	Description
6292104	JES4 B7: commadmin fails to add org due to AMException error
6294603	JES4_07/05 nightly: commadmin fails to create user with -S mail,cal

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

Java Enterprise System Components

The following Java Enterprise System components are required for this release of Delegated Administrator:

Directory Server 5.2
Access Manager 7.0
Either Messaging Server 6 or Calendar Server 6, or both.

For information about requirements for Messaging Server, see Bugs Fixed in This Release.

For information about requirements for Calendar Server, see Known Issues and Limitations.

Java Enterprise System Web container. You must deploy Delegated Administrator to one of the following Web containers:
Sun Java System Web Server 6.1 sp5
Sun Java System Application Server 8.x

LDAP Schema 2. This release of Communications Services Delegated Administrator is designed for provisioning users in an LDAP Schema 2 directory.

For information about requirements for Directory Server, Access Manager, Web Server, and Application Server, see the current release notes for these products.

For installation instructions for the Java Enterprise System components listed in this section, see the Sun Java Enterprise System Installation Guide.

Patch Requirement Information

The following table gives the numbers and minimum versions for the alignment patches. All patches referred to in this section are the minimum version number required for upgrade. It is possible that a new version of the patch has been issued since this document was published. A newer version is indicated by a different version number at the end of the patch. For example: 123456-04 is a newer version of 123456-02 but they are the same patch ID. Refer to the README file for each patch listed for special instructions.

To access the patches, go to http://sunsolve.sun.com.

Table 8  Delegated Administrator 6 2005Q4 Alignment Patches Required for HP-UX

Patch Number	Patch Description
121393-01	HP-UX 11.11: Sun Java™ System Directory Server 5 2005Q4
121931-01	HP-UX 11.11: Sun Java™ System Directory Server 5 2005Q4 (Localization Patch)
121512-02	HP-UX 11.11: Sun Java™ System Calendar Server 6 2005Q4
121511-01	HP-UX 11.11: Sun Java™ System Messaging Server 6.2 2005Q4
121927-01	HP-UX 11.11: Sun Java™ System Messaging Server 6.2 2005Q4 (Localization Patch)
121510-01	HP-UX 11.11: Sun Java™ System Web Server 6.1 2005Q4
121935-01	HP-UX 11.11: Sun Java™ System Web Server 6.1 2005Q4 (Localization Patch)
121514-01	HP-UX 11.11: Sun Java™ System Application Server 8.1 2005Q4
121934-01	HP-UX 11.11: Sun Java™ System Application Server 8.1 2005Q4 (Localization Patch)
121937-01	HP-UX 11.11: Lockhart Localization patch

For detailed information about Upgrade procedure of the Delegated Administrator from JES3 to JES4 refer Sun Java Enterprise System 2005Q4 Upgrade Guide for HP-UX located at http://docs.sun.com/app/docs/doc/819-4460.

Deployment Guidelines

In addition to the utility and console, the Delegated Administrator software includes a server component.

The Delegated Administrator server must be deployed to the Web container used by Access Manager.

The Delegated Administrator console can be deployed to another supported Web container.

Hardware Requirements

The memory and disk space requirements for Delegated Administrator are the same as those of the Web container to which Delegated Administrator is deployed.

For information about the Web container’s hardware requirements, see the current release notes for this Java Enterprise System component.

Browsers

The Delegated Administrator console requires a JavaScript-enabled browser.

Table 9  Delegated Administrator Console Browser Recommendations

Browsers	Solaris 8 for Sparc, Solaris 9 for Sparc, and X86, Solaris 10 for Sparc and X86	Windows 98	Windows 2000	Windows XP	Red Hat Linux 7.2	Macintosh OS X
Netscape™ Communicator	7.1	7.1	7.1	7.1	7.1	7.1
Internet Explorer	N/A	6.0 SP1 or later	6.0 SP1 or later	6.0 SP1 or later	N/A	N/A
Mozilla™	1.4	1.5+	1.5+	1.5+	1.5+	1.5+

Delegated Administrator Known Issues and Limitations

This section contains a list of the known issues and limitations with Delegated Administrator 2005Q4. The following topics are the known issues:

The Domain Disk Quota value is lost if you change the Domain status or Mail Service status of a full organization (6239311)

This problem occurs if you edit a full organization with a Domain Disk Quota value set to any numeric value, and you change the Domain Status or Mail Service Status from Active to any other value (such as Inactive or Hold).

A message indicates that the properties of the organization have been successfully modified, but the value of the Domain Disk Quota field is set to unlimited, and the LDAP attribute (mailDomainDiskQuota) is lost for the organization.

Workaround

Reset the value of the Domain Disk Quota field and save the properties of the organization again.

Server error; administrator is logged out when trying to create a new user or edit an existing user (6234660)

This problem occurs when you open a User page in an organization that contains many users, and you try to create or edit a user while the page is still loading the existing users. While the page is loading, a message asks you to wait. Do not click any buttons or links until the page is ready.

A similar problem occurs when you open an Organization page that contains many organizations.

Workaround

If the User page takes too long to load, you can set the jdapi-wildusersearchresults property to a sufficiently low value to allow the page to load quickly. For example:

If an Organization page takes too long to load, you can set the jdapi-wildorgsearchresults property to a low value. For example:

jdapi-wildorgsearchresults=10

jdapi-wildusersearchresults and jdapi-wildorgsearchresults are properties in the resource.properties file.

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

da_base/data/WEB-INF/classes/sun/comm/cli/server/servlet/resource.properties

On the User Properties page, you cannot uncheck the Forward box, select the Local Inbox, and save the modification (6230702)

If a forwarding address has been specified for a user, you cannot uncheck the Forward box in the User Properties page and check the Local Inbox in one operation.

Workaround

First check the Local Inbox and click Save.

Next, uncheck the Forward box and click Save.

Performance of the Delegated Administrator configuration program (config-commda) is slow if a very large number of organizations are deployed in the directory (6219610)

If the directory contains a very large number of organizations (50,000 or more), the Delegated Administrator configuration program (config-commda) can take a long time to complete. Performance of administrative tasks related to Access Manager is slow.

Workaround

Create a pres, eq index on the ou attribute.

Values in the resource.properties files are overwritten when Delegated Administrator is reconfigured with the config-commda program (6218713)

If you configure an existing, configured installation of Delegated Administrator by running the config-commda program again, the properties in the resource.properties file are reset to their default values.

For example, if you previously set the following properties to these values:

jdapi-wildusersearchresults=50

jdapi-wildorgsearchresults=10

and then run config-commda, these properties would be reset to their default values, as follows:

jdapi-wildusersearchresults=-1

jdapi-wildorgsearchresults=-1

This issue is of concern only if you have changed the Delegated Administrator configuration (if you have enabled plug-ins or modified the values of any properties in the resource.properties file).

Work around

If you need to upgrade Delegated Administrator, or if you need to rerun the config-commda program for any other reason, you can preserve your existing configuration by taking the following steps:

Back up the resource.properties file.

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

da_base/data/WEB-INF/classes/sun/comm/cli/server/servlet/resource.properties

Run the config-commda program.
Edit the new resource.properties file created by the config-commda program, as follows:

(The new file is located in the default path shown in 1. Back up the resource.properties file, above.)

Open the new resource.properties file.
Open your back-up copy of the resource.properties file.
Locate the properties that were customized in the back-up copy. Apply the customized values to the corresponding properties in the new resource.properties file.

Do not simply overwrite the new resource.properties file with the entire back-up copy. The new file may contain new properties created to support this release of Delegated Administrator.

Log-in performance is slow for a TLA logging in to Delegated Administrator in a directory deploying a very large number of organizations (6216904)

If a Top-Level Administrator (TLA) logs in to Delegated Administrator and the directory contains a very large number of organizations (50,000 or more), the log-in can take up to three minutes.

Workaround

Create a pres,eq index on the sunBusinessOrgBase attribute.

The commadmin user modify command fails if you assign both the sunpresenceuser and sunimuser object classes to a user entry (6214638)

Service-package filter causes logout (6211658)

This issue occurs when you take the following steps:

Log in to Delegated Administrator as a Top-Level Administrator (TLA).
Select “All Service Packages.”
In the Filter Option menu, select IMAP or POP.

Delegated Administrator logs out with the following error message: “Unknown error, so logging out. Please check the logs for details.”

Cannot access the “All Service Packages” and “Properties” tabs (6206196)

When you access the “All Service Packages” tab, a Session error message is displayed. When you access the “Properties” tab, the log-in page is displayed instead of “Properties”.

A newly created user does not inherit the domain’s itemizing (TZ) (6206160)

If you create a domain with a non-default itemizing, and then create a new user without explicitly using the -T <timezone \> option, the user is given the default itemizing (America/Denver).

The commadmin domain purge command does not purge calendar resources (6206797)

You need to save the Organization Properties page to successfully add an administrator (6201912)

If you open the Organization Properties page and assign an administrator role to a specified user, you must then save the Organization Properties page to add the administrator successfully. If you log out after assigning the new administrator, the administrator is not added.

A TLA or SPA cannot update the”Alias Names for Domain:” text field for a shared organization (6200351)

This problem occurs if you perform the following procedure:

Log in to the Delegated Administrator console as a TLA or SPA.
Select a shared organization (such as DEF).
Select Properties for this organization from the Show: drop-down list.
Enter valid values in the Alias Names for Domain: text field.
Click Save.

The following message is displayed: “Properties of this Organization have been successfully modified.”

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	The Delegated Administrator for JES 3 Release can be deployed only on Sun Java System Application Server 8.1. as well as Sun java system Web server. 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.

---

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/1312.1
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 � 2006 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.

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 � 2006 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 plus des brevets am�ricains list�s � l'adresse http://www.sun.com/patents et un ou les brevets suppl�mentaires ou les 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.

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 I