Sun Java System Communications Services 2005Q4 Release Notes

Chapter 2 Sun Java System Messaging Server 6 2005Q4 Release Notes

Version 6 2005Q4

These Release Notes contain important information available at the time of release of Sun JavaTM System Messaging Server 6 2005Q4. New features and enhancements, known issues and limitations, and other information are addressed here. Read this document before you begin using Messaging Server 6 2005Q4.

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.

These release notes contain the following sections:

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

Release Notes Revision History

Table 2–1 Sun Java System Messaging Server Revision History


Description of Changes 

July 2005 

Beta release of Sun Java System Messaging Server 6 2005Q4 

October 2005 

Final release of Sun Java System Messaging Server 6 2005Q4 

March 2006 

Listing of documentation updates to Sun Java System Messaging Server Administration Guide.

About Messaging Server 6 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.

What's New in This Release

The following new features and enhancements were added to the Messaging Server 6 2005Q4 release:

The default value for the MISSING_RECIPIENT_POLICY MTA option has been changed from 2 (add envelope recipient list as a To: field) to 1 (ignore missing recipient condition). Messaging Server is now in compliance with RFC 2822.

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 version of Messaging Server.

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

Sieve errors are now logged as such in mail.log when LOG_FILTER is enabled.

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. 

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://http/

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


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.


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

    				  i18n[’sent folder IE’] = ’soushinzumiaitemu’ 
    				  fldr[’Sent Items’] = ’soushinzumiaitemu’
  2. 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.


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:

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


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

Note –

For information about upgrading to Messaging Server 6 2005Q4 from a previous version of Messaging Server, see Installation Notes.

Important Patch Information

For the current list of required patches for Sun Java System Messaging Server go to and select either “Patches” or “Patch Portal”. As operating system patch requirements change and patches to Java Enterprise System components become available, updates will be made available on SunSolve, initially in the form of recommended patch clusters.

Supported Platforms

This release supports the following platforms:

For detailed information about Solaris and Linux requirements, including required upgrade patches and kernel versions, see the Sun Java Enterprise System 2005Q4 Installation Guide for UNIX and Sun Java Enterprise System 2005Q4 Release Notes.

For a list of the Messaging Server packages, see Appendix Appendix A, Java ES Components for This Release, in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX in the Sun Java Enterprise System 2005Q4 Installation Guide for UNIX.

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, throughput is directly related to file system performance. If you have questions about sizing and performance, contact your Sun Java System representative.

Required Patches

For more information on Messaging Server patches, see

Client Software Requirements

Communications Express access for Messaging Server requires a JavaScript-enabled browser. For optimal performance, Sun recommends the browsers listed in this section:

Table 2–2 Messaging Server 6 2005Q4 Client Software Recommendations


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

NetscapeTM Communicator







Internet Explorer 


6.0 SP1 or later 

6.0 SP1 later 

6.0 SP2 










Product Version Compatibility Requirements

Messaging Server is compatible with the product versions listed in this section:

Table 2–3 Product Version Compatibility Requirements



Sun Cluster 


Veritas Cluster Server 

1.3, 2.0, 3.5, 4.0 

Sun Java System Directory Server 

5.1, 5.2 

Sun Java System Access Manager (formerly called Identity Server) 

Compatible (6.x): Supports Access Manager 6 features, including the Access Manager 6 Console and directory information tree (DIT). If you are installing Access Manager with Portal Server, Messaging Server, Calendar Server, Delegated Administrator, or Instant Messaging, you must select the Access Manager Compatible (6.x) installation type.


Enhanced (7.x): Supports Access Manager 7 features, including the new Access Manager 7 Console. Use the Enhanced (7.x) installation type only if you are not installing Portal Server, Messaging Server, Calendar Server, Delegated Administrator, or Instant Messaging.

Sun Java System Web Server 


Sun Java SystemApplication Server 

7.x and 8.x 

NSS Version Requirements

Messaging Server 6 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 2005Q4 Installation Guide for UNIX and Sun Java Enterprise System 2005Q4 Release Notes

Messaging Server Use of Administration Server

Messaging Server uses Administration Server for the following purposes:

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:

If your Internet host table in your /etc/hosts file looks like:

123.456.78.910 budgie loghost mailhost


change it so that there is only one line for the IP address of the host. Be sure the first host name is a fully qualified domain name. For example:

123.456.78.910 budgie loghost mailhost


File System

The following file systems are recommended for message stores:

Installation Notes

These installation notes pertain to the Messaging Server 6 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 for UNIX.

Next, you must configure Messaging Server by:

For configuration instructions, see the Sun Java System Messaging Server 6 2005Q4 Administration Guide

Upgrade Instructions for Messaging Server

If you are upgrading to Messaging Server 6 2005Q4 from an earlier release, follow the upgrade instructions in the Sun Java Enterprise System 2005Q4 Upgrade Guide as well as the Sun Java Enterprise System 2005Q4 Release Notes.

Checking the /etc/hosts file entry

If you are installing Messaging Server for the first time or upgrading from an earlier version of Messaging Server, ensure that you have the following entry in /etc/hosts file on your Solaris system:

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

For Example, budgie

Note –

On Solaris 10 platforms, you not only have to add the Fully Qualified Domain Name (FQDN) to the /etc/hosts file, but also to the /etc/inet/ipnodes file. Otherwise, you will get an error indicating that your host name is not a Fully Qualified Domain Name.

Compatibility Issues

The following table describes compatibility issues with Messaging Server:




Access Manager now has two installation types: Realm (version 7.x style) and Legacy (version 6.x style).  

If you are installing Access Manager with Messaging Server, Calendar Server, Instant Messaging, Delegated Administrator, or Portal Server, you must select Legacy mode (version 6.x style). See: Sun Java System Access Manager 7 2005Q4 Release Notes

If the wrong Access Manager is installed, you will not be able to run Delegated Administrator.  

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

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

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

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

(bug 6275916) 

No workaround. 

No additional comments. 

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

(bug 6303859) 

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

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

In Messaging Server 5.x, an administrator could use the IMAP list command to display all folders in the message store. In a typical message store, this caused the server to display an unusually long list.


In Messaging Server 6.x, when an administrator runs the IMAP list command, it displays only the explicitly shared folders.

To list all folders in the message store, use the mboxutil utility.

For more information on the mboxutil utility, see the Sun Java System Messaging Server 6 2005Q4 Administration Guide.

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

No workaround 

For more information, see For more information on SSO and Access Manager, see:

This release of Communications Express is incompatible with the 2004Q2 version of Calendar Server. 

If you upgrade Communications Express, you must also upgrade Messaging Server. 

This also applies to Calendar Server. 


For more information on Communications Express, see Chapter Chapter 5, Sun Java System Communications Express 6 2005Q4 Release Notes.

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

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

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

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

(bug 6311363) 

On Messenger Express, you are able to use RTF/HTML editing for Internet Explorer browsers. You are unable to use RTF/HTML editing with Mozilla or Netscape browsers. 


In the JES 2 version of Communications Express, you are able to use RTF/HTML editing for Internet Explorer browsers. You are unable to use RTF/HTML editing with Mozilla or Netscape browsers. 


In the JES 3 version of Communications Express, you are able to use RTF/HTML editing for Internet Explorer 5.5 or later, Mozilla 1.3 or later, or Netscape 7.2 or later. 

No additional comments. 

Documentation Updates for Messaging Server 6 2005Q4

This section describes the documentation updates in the Messaging Server 6 2005Q4 documentation set.

The following updates have been made to the Sun Java System Messaging Server 6 2005Q4 Administration Guide:

The S/MIME signature and encryption features were introduced for Communications Express Mail in the Sun Java System Messaging Server 6 2005Q4 Release.

See the Messaging Server Administration Guide for information to administer the signature and encryption features.

How you save an attachment depends on the nature of the message that has the attachment. If the message has an S/MIME signature, was encrypted, or both, use Procedure 1 to save its attachments. Use Procedure 2 if the message does not use the S/MIME features.

Procedure 1 — Saving Attachments for a Message that uses S/MIME

To save an attachment for a message that uses the S/MIME features, follow these steps

  1. Click the name of the attached file in the message header.

  2. The “Save” dialog box appears. In the File Name field, enter the name of the attachment to be saved

  3. Click Save.

Procedure 2 – Saving Attachments for a Message that Does Not Use S/MIME

To save an attachment for a message that does not use the S/MIME feature, follow these steps:

  1. Use the Save As function of your browser to save the attachment. Or, right-click the name of the attached file in the message header. (In the case of GIF or JPEG files, which are displayed in the body of the message, right-click on the image.)

  2. Click Save in the dialog box. Or, choose Save Target As from the drop-down menu.

  3. The “Save As” dialog box appears. In the File Name field, enter the name of the attachment to be saved.

  4. Click Save.

For additional information about Messaging Server, see the Messaging Server 6 2005Q4 documentation, listed in the following sections.

Messaging Server Documents

Use the following URL to see all the Messaging Server 6 2005Q4 documentation

Messaging Server 6 2005Q4 provides the following new and updated documents:

Communications Services Documents

Use either one of the following URLs to see the documentation that applies to all Communications Services 6 2005Q4 products: or

The following documents are available:

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.


No error logged in the default log when mailbox name is invalid.


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


job_controller.cnf missing master_command for hold channel.


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 user cant see the folder.


imsbackup does not backup user defined flags.


ims_info_get_core does not provide detailed error reporting.


System flags are not restored when restoring form SPARC to x86.


Add -i option to imsimport to ignore Content-Length.


Click on shared folder, then click on INBOX get JavaScript error.


Setting mail forwarding is possible without entering a mail forwarding address.


msprobe logs messages to the imta log file imexpire -m dumps core.


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.


spamfilterXoptin broken.


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


start-msg creates error message while testing on NFS.


ims_master dumped core when mailmessagestore LDAP attribute is invalid.


Forwarded message saved as draft appears to lose the forwarded attachment.


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


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


imexpire dumped core when one specifies -m -1


imsimta encode -header -filename with multiple files botches boundary marker.


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


AService program core dump when configuration file permissions incorrect


msuserpurge -v is not listing all users error.


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 andimap 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 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 Messsage in imsbackup should indicate which file is problematic


Granting permission to a mail folder or to an LDAP group expands group to individual members.


Logging RFE: Failed index file open/read message needs more information.


MoveUser removes the folders.


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


start-msg not detecting the presence of SNMP sub-agent


The Job Controller can exit if Ctrl-C is typed at any time after running imsimta refresh.


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 LMTP encounters “all addresses ugly” condition is incomplete


LMTP server shouldn't write debug log output for delivery failures unless debugging is enabled.


Messaging Server Console is unable to start in German, Spanish, simplified Chinese and traditional Chinese languages.


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


Need ims_info_get_core/get_mmp to log error messages from optfile_read.


msuserpurge search timeout error.


mboxutil -o -w file name dumped core when output file cannot be opened/created.


local.webmail.sso.uwcsslport should default to sensible value.


8–bit check flags may be incorrect if no content-type is present.


mgrpMsgPrefixText and mgrpMsgSuffixText not working.


Use of non-default notification arguments can result in unnecessary message copies being made.


store.expirerule.longdays.messagedays can overflow.


Message Store/MMP authentication fails when option.dat begins with an option rather than a comment.


msuserpurge time out on Message Stores with over 20,000 domains.


Incorrect page header for logout when user is connected via Multiplexor.


imexpire -m dumps core.


The unix_purge utility does not work.


ASock_NewBound backlog listen queue is too small.


The script makes tailor file attributes lowercase.


The ability to backup a single message does not work.


Core dump from serverstart command line utility.


MoveUser does not delete empty folders in source mail host when -F option is used.

Known Issues and Limitations

This section contains a list of the known issues with Messaging Server 6 2005Q4. The following product areas are covered:

Installation, Upgrade, and Uninstallation

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

You must use the Java Enterprise System installer to install a cluster agent for Messaging Server. (6175770)

To install Messaging Server in a Sun Cluster environment, you should take the following steps. For a fuller explanation of this procedure, see the Sun Cluster installation example in “Chapter 3: Installation Scenarios” in the Sun Java Enterprise System 6 2005Q4 Installation Guide.

  1. Run the Java Enterprise System installer and select to install the Sun Cluster and Sun Cluster Agents, then choose “Configure later” in the installer.

  2. Configure the Sun Cluster environment. (For details, see the Sun Cluster documentation.)

  3. Run the Java Enterprise System installer again and install Messaging Server (and other component products).

  4. Configure Messaging Server. For details, see the Messaging Server 6 2005Q4 Administration Guide

This version of Messaging Server does not support a staged rolling upgrade with minimum downtime in a symmetric HA environment. (4991650)

With Messaging Server 5.2, you could install the Messaging Server more than once on the same machine and patch the different installations separately. This capability enabled support for minimal-downtime staged rolling upgrades. Messaging Server 6 2004Q2 does not provide this capability.

Messaging Server does not start under SunTM Cluster 3.0 Update 3. (4947465)

Messaging Server cluster agents dump core due to a problem in Sun Cluster 3.0 Update 3. Use Sun Cluster 3.1 to solve this problem.

Messaging Server

This section describes known issues in the Messaging Server product.

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


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

For example, instead of:


You can workaround the problem by adding spaces as follows:


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:


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

Messaging Server fails to start when SNMP is enabled on Solaris 10. (6299309/6290934)


Direct snmpwalk to snmpdx instead of snmpd and go directly to port 16161 instead of port 161.

The imsimta refresh command generates confusing error messages. (6263066)

When the watcher process is enabled, imsimta refresh command generates confusing messages.


Run imsimta cnbuild to compile the configuration. Then, run start-msg. The imsimta refresh command will be deprecated in a future release.

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.


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

  1. Edit imta.cnf file and remove the channel keyword maytlsserver from tcp_local and tcp_intranet channels.

  2. Change the following configutil configuration parameters by setting service.imap.sslusessl to 'no' and service.pop.sslusessl to 'no'.

  3. Recompile the MTA configuration with the imsimta cnbuild command.

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

The configure program fails with non-standard organization DNs. (6194236)

The configure program does not construct intermediate RDNs between the organization DN and the User/Group suffix. This problem occurs both with Schema 1 and Schema 2.


Create the Organization DN prior to running the configure program (or at least to the DN above the Organization DN).

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

When using an HTTP proxy in Internet Explorer 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. (4967344)

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.


To achieve this alternative behavior, change:

         certmap default         default
		 #default:FilterComps    e, uid


		 certmap default         default
		 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).


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

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


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


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.


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)


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.

Connections aborted with TCP_IOC_ABORT_CONN in syslog. (4616287)

If a failover occurs for an HA configuration running Sun Cluster 3.1 on the Solaris 8 U7 or Solaris 9 Operating System and active TCP connections are aborted with the TCP_IOC_ABORT_CONN ioctl, messages such as the following are logged on the console and to system logs.

	Jul 24 16:41:15 shemp ip: TCP_IOC_ABORT_CONN: local =, 
	remote =, start = -2, end = 6
	Jul 24 16:41:15 shemp ip: TCP_IOC_ABORT_CONN: aborted 0 connection

These messages are informational only and should not show up in non-debug mode.

If you use Microsoft Outlook Express as your IMAP mail client, the read and unread flags might not work properly. This is a known problem with the Microsoft Outlook Express client. (4543930)

To enable the workaround, set the following configuration variable:

configutil -o local.imap.immediateflagupdate -v yes

If, while using the workaround, you experience performance issues, it is recommended that you discontinue using the workaround.

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, * 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=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
uniquemember: uid=ofanning,, o=isp

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=isp
changetype: modify
add: memberof
memberof: cn=Service Administrators, ou=groups, o=isp

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


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:

msg_svr_base/sbin/configutil -o local.ugldapbinddn -v "rootdn" -l

msg_svr_base/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


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


Create the symbolic link manually:

ln -s msg_svr_base/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 msg_svr_base/lib/jars/msgadmin62-2_03_ lang.jar msg_svr_base/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).


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


This section describes known issues in the Communications Services and Messaging Server-specific documentation.

Correction to bug 5076486 regarding imadmin user purge with iPlanet Delegated Administrator 1.2 Patch 2 (6307201).

You are able to use the imadmin user purge command with iPlanet Delegated Administrator 1.2 Patch 2 and Messaging Server 6.x. This legacy version of Delegated Administrator should not be confused with the current Delegated Administrator product documented in Chapter Chapter 4, Sun Java System Communications Services Delegated Administrator 6 2005Q4 Release Notes. To use the legacy version of Delegated Administrator, you need to follow the procedures outlined in the iPlanet Delegated Administrator installation documentation on along with the following modification:

Change the MsgSvrN-cgipath line in the iDA_install_directory/nda/classes/netscape/nda/servlet/ file to MsgSvr0–cgipath=msg-config/Tasks/operation and restart the Web Server.

If you are running on a cluster, be sure that the Administration Server is running on the same node as Messaging Server (See bug 6306637 for more information).

No documentation available on new shared defragment database feature. (5091281)

No documentation available on a new feature whereby MTA systems can share the defragment database and thereby defragmentation can be done on MTA systems instead of the store system.

Redistributable Files

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