Sun Java System Messaging Server Release Notes for Microsoft Windows
Sun Java System Messaging Server Release Notes for Microsoft Windows
Version 6.2 2005Q4
Part Number 819-4269-10
These Release Notes contain important information available at the time of release of Sun Java System Messaging Server 6.2 2005Q4 and Sun Java System Communications Services Delegated Administrator 6 2005Q4 for Windows. Known issues and limitations, and other information are addressed here. Read this document before you begin using Messaging Server 6.2 2005Q4 and Delegated Administrator 6 2005Q4.
These release notes contain the following sections:
Third-party URLs are referenced in this document and provide additional, related information.
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
Description of Changes
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 Messaging Server 6.2 2005Q4
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 Sun Java System Communications Services Delegated Administrator 6 20054.
- 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:
(1) Skipped if the address is a mailEquivalentAddress (bit clear)
(2) 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.
Support for the following features may be eliminated in a future release:
The Sun Java System Administration Console has been deprecated and will be removed from the Messaging Server product in a future release.
This section describes the platform, client product, and additional software requirements for this release of Messaging Server:
This release supports:
For detailed information about Windows platform requirements, see the
Sun Java Enterprise System 2005Q4 Release Notes for Microsoft Windows (http://docs.sun.com/doc/819-4261)
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, throughput is directly related to file system performance. If you have questions about sizing and performance, contact your Sun Java System representative.
Client Software Requirements
Table 2 Messaging Server 6 2005Q4 Client Software Recommendations
5.5 or 6.0
1.2 or 1.4
Product Version Compatibility Requirements
Messaging Server is compatible with the product versions listed in the table below:
Table 3 Product Version Compatibility Requirements
Sun Java System Directory Server
5.1, 5.2, 5.2.4
Sun Java System Access Manager
6.1 (Command-line Interface Only)
Sun Java System Web Server
6.1 (but 6.0 Service Pack 5 if you are using iPlanet Delegated Administrator)
NSS Version Requirements
Messaging Server 6.2 2005Q4 requires the use of the shared security component NSS version 3.9.4.
For more details about product version dependencies, see,
- Sun Java Enterprise System Installation Guide for Unix (http://docs.sun.com/app/docs/doc/819-2328)
- Sun Java Enterprise System 2005Q4 Installation Guide for Microsoft Windows (http://docs.sun.com/app/docs/doc/819-4280)
- Sun Java Enterprise System Release Notes (http://docs.sun.com/app/docs/doc/819-4161).
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:
Make sure that the FQDN is the first host name in the \WINNT\system32\drivers\etc\hosts file.
If your Internet host table in your \WINNT\system32\drivers\etc\hosts file has multiple line, like:
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:
Bugs Fixed in This Release
This section describes the bugs fixed in the Messaging Server 6 2005Q4 release.
For a complete list of bugs fixed in this release, see the README file delivered with the Messaging Server core software patch.
Table 4 Fixed Bugs in Messaging Server 6.2 2005Q4
A log records now include authorization information
Packages have a default BASEDIR of /opt
Corrupt Japanese Delivery Reports
SunONE_MsgSvr script echoes unnecessary -n
STATUS command is slow on large fragmented mailbox
French localization: &_agrave; instead accented a in “Mettre a jour” label
Need configuration option to limit number of folders /sub-folders
XFILE: 5090205, tcp_smtp_server dumps core with LDAP over SSL
Notification failure error in amSession log during logging out from Communications Express
Add addresses: does not add all entries into the Personal Address Book
Return job doesn’t recognize messages with urgent priority
Illegal commands can cause imsimta qm to dump core
tcp_smtp_server performance problem (100% CPU utilization)
Upgrade script should deprecate autoreply channel
S/MIME: retry on WMAP commands when HTTP connection lost in Applet
Request limitation on physical number of messages per folder and log message
Console hangs when setting expire rule with header constraints
Include user original over the wire login ID in MMP log output
Quota bar is not right when user is over quota
Accented messages are not being displayed correctly
SMIME message not sent with priority requested
RENAME operation from a personal folder to a shared folder succeeds but
imsbackup does not backup user defined flags
System flags are not restored when restoring form SPARC to x86
Add -i option to imsimport to ignore Content-Length
Setting mail forwarding is possible without entering a mail forwarding address
msprobe logs messages to the imta log file
imsimport is not checking the two leading new lines in From_ line
service.readtimeout should be set to 30 by default
need reconstruct (or some tool) to correct bad store.sub
Multiple packages deliver the same binary for SUNWmsgwm and SUNWmsges
Cannot break the mboxutil -o command
imsrestore restores the INBOX on second attempt when threshold is exceeded
mboxutil -d returns Unknown code __9F 242
stored time out waiting for processes to exit must be finite
immonitor-access appears to calculate IMAP time incorrectly, when combined with SMTP
SNMP sub agent fails to come up.
Going out from mail tab to other tab causes folder tree to disappear
Possible memory corruption when sleepycat transaction fails
reconstruct -m reports fixing quotas, but doesn’t
Memory leaks when opening a corrupted mailbox
Memory leaks in reconstruct when mailbox is corrupted
Utilities should tell the user as well as log that the watcher is not running
Encode unparseable address header fields
Fix mboxutil usage: duplicate entry for -d option, -P not listed as valid parameters to -d
Unread message count disappears when user clicks on View Message Header Detail
imsconnutil -c logs store emergency error when there is no connected user
Can’t start/stop services (IMAP/POP/MTA/HTTP) from Messaging Server console.
Expired encrypting certificate causes valid signature displayed as invalid when viewed by recipient
Encode 8 bits header (sender)
ims_master dumped core when mailmessagestore LDAP attribute is invalid
RFE: Generate a log message automatically when MAX_MESSAGES is exceeded
Mailbox corruption reported when none exists
5.2P2 to 6.2 upgrade: primary partition path is not modified
Upgrade from 5.2P2 to 6.2: make_mta_config_changes.sh fails on certain copy commands
Perform job controller rebuild in such a way that the startup is more fair
Change ICAP request string to avoid 201 response
Spam filter support enhancements for new version of Brightmail
Unable to make a fresh restart of messaging services via administration console after changes
Setting URL_RESULT_CACHE_SIZE to 0 breaks URL result processing
Bookkeeping error counting delayed messages
HTTP daemon crashes on deleting folder after creating a subfolder
immonitor-access -I core dumps when user in hosted domain
reconstruct does not notice all nulls in cache record
Administration Console invoked in German sets expire rule with German for or
imsimport creates mailbox with uppercase domain name
Customer wants to use $subject in his autoreply message
Reconstruct core on Ctrl/C with iBiff
Case sensitive causes problems with reconstruct
imsimta encode -header -filename with multiple files botches boundary marker
Version of comm_dssetup.pl in /opt/SUNWmsgsr/install corrupts Access Manager
$N with no argument in AUTH_REWRITE doesn’t get default error text
Cannot break (Ctrl-C) the msuserpurge command
imsched dumped core during refresh
Audit access control changes on IMAP folders
SNMP shows 0 values for all message access information
job_controller looping in addtopriorityqueue (ETRN)
Garbage in Y records in log files
problems setting large quotas on a user basis
Use heuristic parse to extract address from headers for AUTH_REWRITE
messages will not be dequeued from defragment channel
probe test fails to restart dispatcher daemon after dispatcher daemon is killed
MTA passes “ ” as the quota value to the store when quota information is not available
transactionlimit keyword not working
disconnecttransactionlimit not getting checked at MAIL FROM stage
Regression: tcp_smtp_server and imap both dumped core XFILE 6235303
MMP needs ability to change user search filter within domain when inetDomainSearchFilter is not set
Copying a large message to a folder on another server fails
String concatenate doesn’t guard against append argument being too long
Spamfilter error handling calls wrong routine
iminitquota should check and repair overquota mailuserstatus when overquotastatus is enabled
Setting local.store.overquotastatus to ‘on’ does not enable quotaoverdraft mode automatically
Clean up sieve setdate support
Add support to sieve notify to include original message in new message
mboxutil -o does not list orphan mailboxes that have LDAP entries with different case in the UIDs
Invalid ‘Mailbox corrupted, appears truncated’ error from ims_master
Incorrect message size logged by MTA if message submission is rejected
Missing leading new line in a From line of an exported mailbox
More log info when SMTP connection aborted
Folders to be managed only by privileged accounts with proper ACL semantic
ims_master should defer additional recipients when it detects shutdown time out
imexpire command doesn’t terminate fast enough
Too many msprobe processes hanging around when there is database hang/lock
dbhang/deadlock after running stress for 45 minutes
msprobe not recognizing SSL-only MMP configuration
msprobe need to be able to test SSL ports
Regression: spaces in certmap.conf issuerDN cause parsing error
imsbackup hangs on some Windows folders.
Administration Server: Incorrectly built binary which accesses errno or h_errno directly
Should sanity check service.http.idletimeout
mboxutil operations should log input from -f file
job_controller core null message removefrompriorityqueue after reload
SMS channel may core in header processing (he_) routines
imsexport produces invalid date format in From line
Log Message in imsbackup should indicate which file is problematic
Logging RFE: Failed index file open/read message needs more information.
Messenger Express Multiplexor: user is redirected to the login page if the session ID contains a ’+’ or a ’/’
mshttpd core dump in saslglue_conn_new ()
Messages still send to the store after message store disk availability check enabled
Off by one error in check of ALLOW_TRANSACTIONS_PER_SESSION option
sslconnect dumps core
Return job not passing envelope from address to notification generator
Cannot create a sub folder in a shared folder from another user in a non default domain
MTA SDK may core (SEGV) when dequeueing a message with multiple recipients
MTA SDK envelope recipient address lookup failures
imsimta clbuild fails during postpatch
Out of box installation should not enable SSL
Messages are still appended onto Sent folder via Communications Express even if one is over quota
Multiple notifications are being sent for delayed messages
MTA SDK may report inapt and confusing error codes
Unexpected outstanding SSL handshake message log level needs to be adjusted
Result of PERSONAL_NAMES mapping and LDAP_PERSONAL_NAMES should be automatically quoted if necessary
Need ability to start SMPP PDU sequence numbers at a value other than 0x00000000
Wrong message sent when delivering via LMTP and NOTIFY=SUCCESS set
Messaging Server patch needs to be patch automation friendly
Request for more detailed logging of MMP operations
Trusted circle SSO fails when inetDomainSearchFilter is configured in Messaging Server
Incorrect pthread_cond_timedwait() call may lead to undefined behavior in SMS channel, MTA SDK
Different behavior of imsimta process command on Linux platform
configmsg_init_default() only loads configuration once
iminitquota should issue right error message instead of “Unknown code __9F 242”
Running stored from a directory not readable by mailsrv user can cause database log accumulation error
imsrestore -n does not work
Messages appearing in MTA debug logs without master_debug keyword specified
Vacation messages are sent with a spurious line break every 1024 characters
History line written when LMPT encounters all address ugly condition is incomplete
Typography mistake in ULA database: ’signing cert’ instead of ’signing certificate
readership command fails with a folder in Japanese characters
Inner forcing text mode processing of text mime types
mshttpd cores - free calls abort in dm_dispose_result after fix for bug 6269460
Job Controller client API does not correctly handle read errors
Job Controller can hang in readline() when transmitted data contains a NUL
MMP logfiles become unreadable due to missing CR
msprobe reporting Unable to open AService.cfg
This section covers the following topics:
These installation notes pertain to the Messaging Server 6.2 2005Q4 release:
Installation Overview for Messaging Server
Use the Sun Java Enterprise System 2005Q4 Installer to install Messaging Server.
For installation instructions, see the Sun Java Enterprise System 2005Q4 Installation Guide for Microsoft Windows.
Next, you must configure Messaging Server by,
Checking the \etc\hosts file entry
If you are installing Messaging Server for the first time, ensure that you have the following entry in \WINNT\system32\drivers\etc\hosts file on your Windows system:
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 5 Messaging Server 6.2 2005Q4 Alignment Patches Required For Windows
Windows (MSI): Directory Preparation Tool
Windows (MSI): Shared Components
Windows (MSI): Sun Java System Messaging Server 6.2 2005Q4
For detailed information about Upgrade procedure of the Messaging Server from JES3 to JES4 refer Sun Java Enterprise System 2005Q4 Upgrade Guide for Microsoft Windows located at http://docs.sun.com/app/docs/doc/819-4461.
Installation Overview for Delegated Administrator
To install Delegated Administrator, use the Sun Java Enterprise System 2005Q4 Installer to install the following components:
The Delegated Administrator software is installed together with Access Manager.
For installation instructions, see the Sun Java Enterprise System 2005Q4 Installation Guide
Next, you must configure Delegated Administrator by
For post-installation configuration instructions, see the Sun Java System Communications Services Delegated Administrator Guide.
- 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.0. 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. (DA does not support Web Server 6.1.)
- While the preferred single-sign on (SSO) method is the one provided by Sun Java System Access Manager, 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.
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 Updates for Messaging Server 6.2 2005Q4
These Release Notes are the only document published with the Communications Services 6.2 2005Q4 release.
Messaging Server Documents
Use the following URL to see all the Messaging Server 6.2 2005Q4 documentation:
Messaging Server 6.2 2005Q4 provides the following documents:
Communications Services Documents
Use either one of the following URLs to see the documentation that applies to all Communications Services 6.2 2005Q4 products:
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 Messaging Server 6.2 2005Q4 for Windows.
This section comprises the following topics:
- Messaging Server service logon should be changed to the current logged on user. This is necessary since the user should have enough privileges to start/stop the server using the Service Control Manager.
- The Administration Server’s http service logon should be changed to logged on user. This is necessary to privilege the admin console to start/stop the servers.
Active Perl 5.8.3 is required to be pre-installed on the system if Instant Messaging, Messaging Server and Calendar Server are selected for installation. (6293991)
Connection Timeout errors during load conditions on Windows (6295747)
Connection Timeout errors occur during load conditions on Windows.
- Create a file named ims-ms_option and write DELIVER_THEADS=5. Place the file under <server-root>\config directory.
- Follow the steps below on OS tuning for Messaging Server under heavy load:
Certain kernel parameters should be modified to optimize performance for the Sun Java System Messaging Server on Windows 2000 Advanced Server.
- Edit the registry entries as given below:
- Set the Performance option to Application in System Properties
Dispatcher hangs during Configure Automatically During Installation in Microsoft Windows XP (6278215), Microsoft Windows 2003 (6336350)
During Configure Automatically During Installation, the default ports for imap and pop are configured to 1143 and 1110 respectively. The mmp ports for imap and pop are 143 and 110 respectively.
To change the ports:
The following redistributable files are provided with Messaging Server 6.2:
- 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:
- The following files are provided solely as reference for writing programs that use the documented API to integrate with Messaging Server:
Sun Java System Communications Services Delegated Administrator 6 20054
These Release Notes contain important information available at the time of release of Messaging Server Communications Services Delegated Administrator 6.3 2005Q4 for Windows. Known issues and limitations, and other information are addressed here.
These release notes contains the following sections:
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:
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 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.
Delegated Administrator Supported Browsers
Delegated Administrator can be viewed using:
Java Enterprise System Components
The following Java Enterprise System components are required for this release of Delegated Administrator:
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.
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.
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.
Table 7 Delegated Administrator Console Browser Recommendations
Solaris 8 for Sparc, Solaris 9 for Sparc, and X86, Solaris 10 for Sparc and X86
6.0 SP1 or later
6.0 SP1 later
Known Issues and Limitations
This section contains a list of the known issues and limitations with Delegated Administrator 2005Q4.
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.
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-wildusersearchresults and jdapi-wildorgsearchresults are properties in the resource.properties file.
The resource.properties file is located in the following default path:
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.
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:
and then run config-commda, these properties would be reset to their default values, as follows:
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).
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:
- 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 Step 1. Back up the resource.properties file, above.)
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.
A newly created user does not inherit the domain’s timezone (TZ) (6206160)
If you create a domain with a non-default timezone, and then create a new user without explicitly using the -T <timezone \> option, the user is given the default timezone (America/Denver).
For example, assume you create a domain named sesta with a timezone of Europe/Paris. Next, create a new user in sesta. The user is given the default timezone, America/Denver.
When you create or modify a user, pass -T < timezone\> explicitly to the commadmin user create or commadmin user modify command.
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.
If you remove all Service packages from a user in an organization and then assign a new Service package from the Service Packages page, the new Service package assignment fails (6198361)
This problem occurs if all Service packages are removed from a user and then you add a Service package to that user from the Service Packages page.
You can add a new Service package to a user in either of the following cases:
Take the following steps:
New non-ascii organizations cause an error because the default administrator’s email address cannot be specified (6195040)
The default administrator’s uid defaults to “admin_ new_organization_name.” If the new organization name contains non-ascii characters, the email address that uses this uid is invalid.
Removing a Service package from an organization causes the following message to be displayed: “No changes in service packages allocation.” (6190486)
If you remove a Service package from an organization and click Save, the service package is removed, but the “No changes in service packages allocation” message is erroneously displayed.
The Shared Organization window does not display available domain names to the Service Provider Administrator (6182985)
When a Service Provider Administrator (SPA) logs in to the Delegated Administrator console and views a shared organization, the Domain Name field in the console does not display the currently assigned domain names.
These domain names should be the values currently assigned to this organization in the sunAvailableDomainNames attribute.
Further, the console should allow the SPA to assign additional domain names to the organization (add domain name values to the sunAvailableDomainNames attribute) from the list of domain names available in the SPA’s provider organization node. The domain names available from the provider organization are contained in the sunAssignableDomainNames attributes.
You cannot edit a user’s login ID in this release of Delegated Administrator (6178850)
If the root suffix name is the same as an organization domain name, the Delegated Administrator utility does not work (5107441)
If you create the root suffix name that is the same as your domain name (for example, if the root suffix is o=example.com and the domain is example.com), the commadmin utilities do not work.
Avoid using the same name for the root suffix and another domain in the directory. (The o=name values must be different.)
The advanced search feature does not return correct results for organizations. (5094680)
This issue occurs if you perform the following steps:
Instead of returning only the organizations that match the search criteria, Delegated Administrator displays all organizations.
The Summary page in the New Organization wizard does not display all the organization details (5087980)
When you create a new organization with the New Organization wizard, certain details, such as Disk Domain Quota and Mail Service Status, are not displayed in the wizard’s Summary page.
Cannot modify non-ASCII groups (4934768)
If a group is created with a group name that contains non-ASCII characters, it cannot be modified with the commadmin group modify command.
For example, if a group with the non-ASCII characters XYZ is specified with the -G option in the commadmin group create command, an email address of XYZ is automatically added to the group’s LDAP entry. Since non-ASCII characters are not allowed in email addresses, modifying the group with commadmin group modify fails.
Use the -E email option when creating a group. This option will specify the group’s email address. For example: commadmin group create -D admin -w password -d siroe.com -G XYZ -S mail \\ -E firstname.lastname@example.org.
Creating a group with multiple -f options adds only one attribute (4931958)
If you specify multiple -f options for creating dynamic groups in the commadmin group create command, only the value specified with the last -f option is added to the LDAP entry. The other values are not added.
Do not specify the -f option multiple times when using the commadmin group create command.
This section describes Delegated Administrator localization bugs.
Delegated Administrator: An error message, “The organization already exists,” is not localized (6201623)
If you attempt to create an organization with the same name as an existing organization, Delegated Administrator displays the following error message: “The organization already exists.” This message appears in English and is not translated.
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
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
You might also find it useful to subscribe to the Sun Java System Communications products customer newsletter for periodic updates from the product team about products and upcoming events. Subscribe at http://subscriptions.sun.com/comms/mailinglist.html.
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 book or at the top of the document. For example, the title of this book is Sun Java System Messaging Server 6.2 2005Q4 Release Notes for Microsoft Windows, and the part number is 819-4269-10.
Additional Sun Resources
Useful Sun Java System information can be found at the following Internet locations:
- Documentation for Sun Java System Messaging Server
- Sun Java System Documentation
- Sun Java System Professional Services
- Sun Java System Software Products and Service
- Sun Java System Software Support Services
- Sun Java System Support and Knowledge Base
- Sun training and support
- Sun Java System Consulting and Professional Services
- Sun Developer Information
- Sun Developer Support Services
- Sun Software Data Sheets
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.
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 � 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 plusieurs des brevets am�ricains list�s � l'adresse http://www.sun.com/patents 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.