View Source

h1. What's New in This Release of Communications Suite 6 Update 2

This document summarizes all features in Sun Java Communications Suite 6 Update 2, Sun Java Communications Suite 6 Update 1, and Sun Java Communications Suite 6 that are new or have been enhanced since Sun Java Communications Suite was originally distributed in March 2007, for the following components:
* Sun Java System Calendar Server 6.3
* Sun Convergence 1 Update 2
* Sun Java System Messaging Server 7 Update 2
* Sun Java System Instant Messaging 8 Update 1
* Sun Java System Delegated Administrator 7
* Sun Java System Communications Express 6.3
* Sun Java System Connector for Microsoft Outlook 7.3 Update 1

This document contains the following sections:
{toc:minLevel=2|maxLevel=2|location=top|type=list}
{anchor:WhatsNewCommSuite}

h2. What's New in Communications Suite 6 Update 2

Communications Suite 6 Update 2 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Upgrading to Communications Suite 6 Update 2

If you choose to upgrade to Communications 6, see the _[Communications Suite 6 Update 2 Upgrade Guide]_.

h4. System Virtualization Support

See [System Virtualization Support in Sun Java System Products|http://docs.sun.com/source/820-4651/index.html] for a summary of Sun support for Sun Java System products and Sun Java suites, including Sun Java Communications Suite, when used in conjunction with system virtualization products and features.

h4. Updates to comm_dssetup.pl

The {{comm_dssetup.pl}} script has been updated to include support for OpenSSO and to add schema for Instant Messaging.

{toc-zone}

h2. What's New in Sun Convergence 1 Update 2

Convergence 1 Update 2 includes the following changes and new features:

{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Performance Improvements
Sun Convergence 1 Update 2 comes with performance improvements for the following components:
* Mail Component -- The performance improvements include decrease in load time when composing and replying to messages.
* Calendar Component -- The performance improvements include several bug fixes and resolution of several memory leak issues.

h4. Shared/Subscribed folders

Users can now share their mail folders with other users or subscribe to other user's shared mail folders. To learn more about how to share a mail folder or subscribe to a shared folder, see the online help.

h4. Mail Quota Usage Information

Sun Convergence now allows users to see their quota usage information. If users have unlimited quota, they do not see any usage information. Administrators can provision user quotas. Appropriate warning is displayed to the user when quota usage reaches 100%. To know more about how to see your mail quota, see the online help.

h4. Auto Spell Checking of Email

Sun Convergence enables you to perform a spell check automatically before sending email. To enable this feature, select the "Always spell check before sending a message" option from the General Mail Preferences. After you enable the spell-check feature, your email will be checked for spelling mistakes before you send the email. For more information about setting the spell-check feature, see the online help.

h4. Spam Feedback

Spam messages are unsolicited bulk emails that you get in your mailbox. You can mark messages as spam or not spam from the mail user interface. This feature enables Convergence users to provide feedback on messages that they think are spam. A spam filter needs to be configured at the back-end Messaging Server. Messages that are marked as spam or not spam are then forwarded to the anti spam filter for appropriate actions.

To know more about how to mark messages as spam or not spam, see the online help. To know more about how to configure handling spam messages, see [Enabling the Spam Feature | CommSuite6U2RR042809:Sun Convergence Administrative Tasks#EnablingtheSpamFeature].

h4. Single SignOn and Authentication using Sun OpenSSO Enterprise 8.0

Sun Convergence 1 Update 2 now supports OpenSSO Enterprise 8.0 for authentication and Single SignOn. To know more about how to do this, see [CommSuite:Configuring Sun Convergence With Sun OpenSSO Enterprise 8.0 for Authentication and SSO].

{toc-zone}

h2. What's New in Messaging Server 7 Update 2

Messaging Server 7 Update 2 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Internal Version Number

The internal version number (displayed in various places like the SMTP and IMAP banner) is now 7u2-x.yy (was 7.0-3.01 for 7 Update 1). The number 2 in 7u2-x.yy now signifies the update number to help associate specific releases with the update release it was based on.

h4. Microsoft Exchange Journaling Format

Messaging Server 7 Update 2 supports the Microsoft Exchange Journaling Format, enabling integration with [ZLTI|http://www.zlti.com/]'s archiving software.

h4. Update of MTA ClamAV Filter Plugin to Support New {{INSTREAM}} Command

The following table shows the new option for the ClamAV option file, its description, and default value.

||Option||Description||Default||
|{{USE_INSTREAM}}|Enables (1) or disables (0) the use of {{INSTREAM}} scanning in {{clamd}}. Starting with ClamAV 0.95, {{clamd}} fixed the deficient design that required two TCP connections to be made when scanning a data stream (control connection and data connection). Now only a single connection is needed which allows for simpler and faster processing (no setup/processing/teardown of data connection) and also allows ClamAV to scale horizontally by placing multiple scanning systems behind load balancers. Attempting to use this option with an earlier version of ClamAV will result in a scanning failure.|0|

h4. Redesign of the ENS Client and Server

The Event Notification Service server and client were redesigned in this release. There is a new client API ({{ens.h}}) that is backwards compatible. The previous ENS server is installed under the name {{enpd1}} for customers who may wish to use it.

h4. Enhancements to the {{reconstruct}} Command

{{reconstruct -a}} attempts to rebuild most aspects of a user's folder, thereby eliminating the need to run multiple commands (such as {{reconstruct -m}} then {{reconstruct -r}}. Since {{reconstruct -a}} rebuilds the entire folder, it was time consuming.

To rectify this, {{reconstruct -a}} now performs a consistency check on each folder in order to determine whether or not to reparse all the messages along with various other repairs. If you run {{reconstruct -a -f}}, a full repair and reparse is forced. If you run {{reconstruct -a -n}}, only a consistency check is run, printing out errors found in the folder. This may be useful in order to catch issues before fixing them.

h4. {{LOG_ACTION}} Mapping Table

The {{LOG_ACTION}} mapping table provides a way for any transactions recorded by the MTA to also, as a side-effect, trigger other effects. A great deal of information, of different types, can be reported in the MTA's message transaction and connection transaction log files. Sites may be interested in noticing certain sorts of transaction log entries as evidence of certain sorts of occurrences, or counting (or at least monitoring trends for) certain sorts of occurrences, or making access decisions based on certain sorts of occurrences. The {{LOG_ACTION}} mapping table provides a way to turn MTA message transaction and connection transaction log file entries into syslog notices, or into MeterMaid counter updates; or if a site wishes to provide their own routine for the mapping table to call, to take whatever, site-defined "action" the site chooses, based upon relevant transaction log entries. For instance, a site might want to notice (via a syslog notice) failed SMTP AUTH attempts as a warning of possible account break-in attempt; or a site might want to count (via MeterMaid) the number of failed (bad) recipients for users' outgoing messages, and react to "high" numbers as a possible sign of a user sending spam with a poor-quality recipient list.

h4. Phase 1 of IPv6 Support

Phase 1 of IPv6 is supported in this release of Messaging Server. As part of this change, the MMP now uses the OS resolver when connecting to other servers and does so synchronously. If you have a server deployment that results in DNS or connection timed out errors to back-end servers (LDAP, mail store), the MMP's {{NumThreads}} parameter should be increased to compensate.

h4. Change In Behavior of Messaging Server HA Upgrade and Configuration

After configuring Messaging Server 7 Update 2 for HA or upgrading to Messaging Server 7 Update 2 in HA, if you are using a compiled configuration, you must recompile the configuration by issuing the command:

{{# imsimta cnbuild}}

Otherwise, the Messaging Server will fail to start in the HA environment. In previous versions, the Messaging Server would run using the older compiled configuration.

{excerpt:hidden=true}
h4. Support For the Sieve Body Test

Support for the Sieve body test, specified in RFC 5173 has been added. There are, however, a number of important restrictions on this support:

* The only match types supported are {{:contains}} and {{:is}}; {{:matches}} and :regex are not supported. This should be considered a permanent restriction due to the possible performance impact of supporting these match types.

* The only body transforms supported are {{:raw}} and {{:text}}; {{:content}} is not supported. This restriction may be removed in a future release.

* Variable substitutions are not allowed in body test arguments. If they are used, an error is likely to occur. For example, this script will fail:

{code}
require ["variables", "body"];
set "a" "testing"
if body :contains "${a}" { discard; }
{code}

This restriction exists so that a list of all arguments to {{body}} in all scripts can be computed in advance and searched for in a single pass. If this restriction were lifted, it would be easy to construct scripts that require an arbitrary number of passes over the message, which is unacceptable in a server environment. As such, this should be considered to be a permanent restriction.

* The {{:text body}} transform operates on all message parts with a text type or a 7bit/8bit encoding. If a charset other than utf-8 is specified on a text part, that part is converted to utf-8 before being searched.

The availability of the body test is controlled by the {{ENABLE_SIEVE_BODY}} MTA option. A value of 0, the default, disables the extension. A value of 1 enables the extension for use in all sieves. A value of 2 enables the use of body in system-level sieves only.
{excerpt}

{toc-zone}

h2. What's New in Instant Messaging 8 Update 1

Instant Messaging 8 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Yahoo Gateway in Instant Messaging
Sun Java System Instant Messaging 8 Update 1 co-packages a gateway for Yahoo messaging clients. The gateway enables Sun Java System Instant Messaging users to communicate with their contacts on Yahoo. This feature enables easy installation and configuration of the Yahoo gateway with Sun Java System Instant Messaging. You can configure the gateway by using the {{configure}} utility.

{toc-zone}


h2. What's New in Delegated Administrator 7

Delegated Administrator 7 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Direct LDAP Access to the Directory

There are two choices for accessing the directory with Delegated Administrator:

* Direct LDAP access to the directory
* Directory access through Access Manager (Legacy Mode)

In this release, by default, Delegated Administrator accesses the directory through direct LDAP calls. By using direct LDAP access, Delegated Administrator removes the former dependence on Access Manager. You can now provision Communications Suite domains, users, and groups without installing or using Access Manager.

Alternatively, you can continue to use the old access method, via Access Manager.

* You can provision objects in a Schema 1 or Schema 2 directory
* You can use Access Manager (Realm mode) with the Communications Suite products (including Delegated Administrator)
* You can run Delegated Administrator, and any other Communications Suites product, without installing or using Access Manager

To take advantage of these choices, you must

* Select "Direct LDAP access to the directory (DL)" when you run the Delegated Administrator configuration program, {{config-commda}}

h4. Support for Schema 1

Delegated Administrator supports provisioning domains, users, and groups in a Schema 1 directory. To enable Schema 1, you must

* Select "Direct LDAP access to the directory (DL)" when you run the Delegated Administrator configuration program, {{config-commda}}

{excerpt:hidden=true}

h4. Support for Access Manager (Realm Mode)

Delegated Administrator is compatible with Access Manager in Realm Mode; thus, you can use Access Manager in Realm Mode for authentication and SSO and use Delegated Administrator. To support Access Manager in Realm Mode, you must

* Select "Direct LDAP access to the directory (DL)" when you run the Delegated Administrator configuration program, {{config-commda}}

{excerpt}

h4. Custom User Attributes Can Be Added to the Delegated Administrator Console

You can add custom user attributes that can be provisioned in the Delegated Administrator console. The custom attributes must belong to your LDAP schema before you can add and use the attributes via the Delegated Adminstrator console.

For more information about this feature, see [Customizing the Delegated Administrator Console|CommSuite:Customizing Delegated Administrator#GEJMV].

h4. Preserving Customized Configuration During Upgrades

Now you can run a merge utility, {{damerge}}, to preserve your customized configuration after you upgrade Delegated Administrator and run the Delegated Administrator configuration program.

When you upgrade Delegated Administrator and run the Delegated Administrator configuration program, the properties in the configuration files are reset to the default values for the new release. However, you can replace the default values with your earlier, customized configuration by using the {{damerge}} utility.

For more information about this feature, see [Preserving Delegated Administrator Customizations During Upgrades|Preserving Delegated Administrator Customizations During Upgrades].

{toc-zone}

h2. What's New in Connector for Outlook 7.3 Update 1 (Patch 139162-02)

Connector for Outlook 7.3 Update 1 patch 139162-02 does not have any new features.
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

Bug Fixes Only.

{toc-zone}

h2. What's New in Communications Express 6.3

Communications Express 6.3 includes the following changes:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Login Access to Access Manager From Within Communications Express

You can now login to Access Manager directly from Communications Express. To do this, you must set either of the following parameters in the {{uwcauth.properties}} file:
* {{uwcauth.identity.login.url}}
* {{uwcauth.identity.ssl.login.url}}

If you have enabled identity, then you must set the above parameters to avoid receiving error messages when you login.

This configuration would only be possible if you have enabled Access Manager by setting the {{uwcauth.identity.enabled}} parameter to "true" in the {{uwcauth.properties}} file.

{toc-zone}

h2. What's New in Communications Suite 6 Update 1

Communications Suite 6 Update 1 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Upgrading to Communications Suite 6 Update 1

If you choose to upgrade to Communications 6, see the _[Communications Suite 6 Update 2 Upgrade Guide]_.


h4. System Virtualization Support

System virtualization is a technology that enables multiple operating system (OS) instances to execute independently on shared hardware. Functionally, software deployed to an OS hosted in a virtualized environment is generally unaware that the underlying platform has been virtualized. Sun performs testing of its Sun Java System products on select system virtualization and OS combinations to help validate that the Sun Java System products continue to function on properly sized and configured virtualized environments as they do on non-virtualized systems.

Communications Suite supports the VMware container (VMware ESX Server 3). As support for other virtulization platforms (LDOMs, xVM Server, and so on) becomes available we will update this document.

For information about Sun support for Sun Java System products in virtualized environments, see http://docs.sun.com/doc/820-4651.

{toc-zone}

h2. What's New in Convergence 1 Update 1

Convergence 1 Update 1 includes the following changes and new features:

{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Support for Domain-Based Client Templates

Convergence 1 Update 1 supports domain based client templates. If your Convergence deployment includes multiple domains, users can log in to a specific domain without specifying the domain information in the user ID. The Convergence server identifies the correct domain-specific pages from the URL and presents it to the client. For more information, see [Deployment Specific Customizable Client Options for Convergence|CommSuite:Sun Convergence Administrative Tasks#Deployment Specific Customizable Client Options for Convergence].

h4. Corporate Directory

The following enhancements have been made to the Corporate Directory functionality of Sun Convergence 1 Update 1.

h5. VLV Index Support

Convergence 1 Update 1 now supports VLV (Virtual List View) indexing. Directory Server provides a mechanism to create indexes. These indexes improve the turnaround time for searching entries in the Directory Server instance. To know more about how to work with VLV indexing, see [How do I configure VLV (Virtual List View) browsing indexes for Directory Server?| CommSuite:Sun Convergence Administrative Tasks#How do I configure Convergence to use separate Directory Server for user authentication and another to store User/Group information?].

{toc-zone}


{anchor:WhatsNewMsgSvr}

h2. What's New in Messaging Server 7 Update 1

Messaging Server 7 Update 1 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Berkeley Database Upgrade

In Messaging Server 7 Update 1, the Berkeley database has been updated from version 4.4.20 to 4.7.25. In order to upgrade the database, {{stored -r}} needs to be run before the new libraries and binaries are replaced because the transaction log file format has changed, and the new libraries will not be able to read them, and thus the database cannot be opened. {{stored -r}} runs automatically during the upgrade process.

For more information about upgrading and downgrading the Berkeley Database, see [Upgrading and Downgrading the Berkeley Database (BDB)|CommSuite:Upgrading the Message Store#Upgrading and Downgrading the Berkeley Database (BDB)].


h4. Password Obfuscation in S/MIME

It is possible to obfuscate passwords with base64 by modifying the {{crlurlloginpw}} and {{loginpw}} configuration parameters in the {{smime.conf}} file.

For more information about this feature, see [CommSuite:Messaging Server smime.conf Parameters].


{excerpt:hidden=true}
h4. Updated Support for Vacation Option Settings in Convergence
{excerpt}


h4. MMP Logging

In previous versions of Messaging Server, the logging subsystem for the MMP was different from the logging subsystem used by IMAP, POP and other components of the message store. This meant that some facilities and options available for controlling logging for the IMAP and POP servers were not available for the MMP.

In Messaging Server 7 Update 1, MMP logging has changed. By default, it uses the same logging subsystem as other message store components. Logging can therefore be controlled in the same way.

For the new MMP logging subsystem, there are a number of new configuration options available for the MMP. The following table shows the new MMP options and their description:

||Option||Description ||
|{{expiretime}}|Same meaning and default as other IMAP and POP logs|
|{{flushinterval}}|Same meaning and default as other IMAP and POP logs|
|{{logtype}}|Same meaning and default as other IMAP and POP logs|
|{{maxlogfilesize}}|Same meaning and default as other IMAP and POP logs|
|{{maxlogsize}}|Same meaning and default as other IMAP and POP logs|
|{{rollovertime}}|Same meaning and default as other IMAP and POP logs|
|{{syslogfacility}}|Same meaning and default as other IMAP and POP logs|
|{{usenslog}}|Defines whether to use the new or old logging system. Setting this to {{true}} causes the MMP to use the same logging subsystem as the message store POP, IMAP and SMTP components. Setting this to {{false}} causes the MMP to use the same behavior as in previous releases. If {{usenslog}} is set to true, the MMP log files are {{mmp}}, {{ImapProxy}}, {{PopProxy}}, and {{SmtpProxy}}.
Default: {{true}}

The following table shows the configuration files for which the new options are available:

||File ||Description ||
|{{AService.cfg}} |Configuration file specifying which services to start and a few options shared by POP, IMAP, and SMTP services. If a log-related setting is made in {{AService.cfg}}, then all three services will inherit that setting by default unless their configuration explicitly overrides it.|
|{{PopProxyAService.cfg}} |Configuration file specifying configuration variables used for POP services. |
|{{ImapProxyAService.cfg}} |Configuration file specifying configuration variables used for IMAP services. |
|{{SmtpProxyAService.cfg}} |Optional configuration file specifying configuration variables used for SMTP proxy services. Required if you enable POP before SMTP; useful for maximizing support for SSL hardware even if POP before SMTP is not enabled. |

You can return to the previous behavior by adding {{default:useNslog 0}} to the {{AService.cfg}} file. Or you can control the new behavior by setting values such as {{default:maxlogfilesize NNN}}.

h4. Changes to the Job Controller and Dispatcher

The job controller and dispatcher are now part of the compiled configuration. In order for changes made to the {{dispatcher.cnf}} and {{job_controller.cnf}} files to take effect, you must recompile the configuration and restart the component by issuing the following commands:

{code}
imsimta cnbuild
imsimta restart dispatcher
imsimta restart job_controller
{code}

{toc-zone}

{anchor:WhatsNewInsMsg}

h2. What's New in Instant Messaging 8

Instant Messaging 8 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. SMS Gateway for Instant Messaging

The SMS (Short Message Service) gateway feature enables the Instant Messaging server to deliver chat messages and alerts in the form of SMS to the Instant Messaging users who are offline. This feature provides streamlined instant messaging experience to users by forwarding messages to the users' mobile phones when they are offline. The SMS gateway uses the SMPP (short message peer-to-peer) protocol and XMPP (Extensible Messaging and Presence Protocol) for messaging services.

For more information, see [CommSuite:SMS Gateway for Instant Messaging].

h4. Multi-User Chat Support for IMPS

Instant Messaging provides a multiuser chat feature for mobile devices that support IMPS. To enable the multiuser chat feature, Instant Messaging uses Extensible Messaging and Presence Protocol (XMPP). Multiple XMPP users can exchange messages in the context of a conference room or channel. In addition to the chat room features such as room topics and invitations, the XMPP protocol enables the ability to kick and ban users from a conference, name room moderators and administrators, and provide different types of membership.

For more information, see [CommSuite:Multiuser Chat Support for IMPS].

h4. Support for AIM and MSN Gateways

Instant Messaging co-packages the gateways for AIM (AOL Instant Messaging) and MSN messaging clients. The gateways enable Sun Java System Instant Messaging users to communicate with their contacts on AIM and MSN. Co-packaging the gateways enables easy installation and configuration of the gateways with Sun Java System Instant Messaging. You can configure the gateway by using the configure utility.

{info:title=Note} Updates to gateways will be provided if and when the open-source community develops them. {info}

For more information, see the [CommSuite:Gateways for AIM, MSN, and Yahoo].

h4. User Initiated Archiving
Instant Messaging provides the users of the Instant Messaging client the ability to archive chat messages. Messages exchanged between two or more users and those exchanged in a conference chat are archived. Messages are archived in the form of emails.

For more information. refer to the Instant Messaging version 8 online help.

{toc-zone}

{excerpt:hidden=true}
{anchor:WhatsNewDA}

h2. What's New in Delegated Administrator 7

Delegated Administrator 7 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Direct LDAP Access to the Directory

There are two choices for accessing the directory with Delegated Administrator:

* Direct LDAP access to the directory
* Directory access through Access Manager (Legacy Mode)

In this release, by default, Delegated Administrator accesses the directory through direct LDAP calls. By using direct LDAP access, Delegated Administrator removes the former dependence on Access Manager. You can now provision Communications Suite domains, users, and groups without installing or using Access Manager.

Alternatively, you can continue to use the old access method, via Access Manager.

* You can provision objects in a Schema 1 or Schema 2 directory
* You can use Access Manager (Realm mode) with the Communications Suite products (including Delegated Administrator)
* You can run Delegated Administrator, and any other Communications Suites product, without installing or using Access Manager

To take advantage of these choices, you must

* Select "Direct LDAP access to the directory (DL)" when you run the Delegated Administrator configuration program, {{config-commda}}

h4. Support for Schema 1

Delegated Administrator supports provisioning domains, users, and groups in a Schema 1 directory. To enable Schema 1, you must

* Select "Direct LDAP access to the directory (DL)" when you run the Delegated Administrator configuration program, {{config-commda}}

h4. Support for Access Manager (Realm Mode)

Delegated Administrator is compatible with Access Manager in Realm Mode; thus, you can use Access Manager in Realm Mode for authentication and SSO and use Delegated Administrator. To support Access Manager in Realm Mode, you must

* Select "Direct LDAP access to the directory (DL)" when you run the Delegated Administrator configuration program, {{config-commda}}

h4. Custom User Attributes Can Be Added to the Delegated Administrator Console

You can add custom user attributes that can be provisioned in the Delegated Administrator console. The custom attributes must belong to your LDAP schema before you can add and use the attributes via the Delegated Adminstrator console.

For more information about this feature, see [Customizing the Delegated Administrator Console|CommSuite:Customizing Delegated Administrator#GEJMV].

h4. Preserving Customized Configuration During Upgrades

Now you can run a merge utility, {{damerge}}, to preserve your customized configuration after you upgrade Delegated Administrator and run the Delegated Administrator configuration program.

When you upgrade Delegated Administrator and run the Delegated Administrator configuration program, the properties in the configuration files are reset to the default values for the new release. However, you can replace the default values with your earlier, customized configuration by using the {{damerge}} utility.

For more information about this feature, see [Preserving Delegated Administrator Customizations During Upgrades].
{toc-zone}
{excerpt}

{anchor:WhatsNewConOutook}

h2. What's New in Connector for Outlook 7.3 Update 1

Connector for Outlook 7.3 Update 1 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Mail Filters and Out of Office Messages

Outlook Connector now provides you with a new User Interface to configure mail filters and vacation messages.

You can use Mail filters feature to organize your incoming mails such that they move into different logical folders in your mailbox based on custom conditions. You can also configure Outlook Connector to copy, forward, or discard the incoming mails.

You can now set an out of office message whenever you are on vacation. This auto-reply system enables you to send a message to the senders (internal and external) of email in your absence.

h4. Contact Picture Support

You can now upload pictures of any format and size to a contact in Outlook Connector. The contact picture is stored on the address book server and can be viewed from the Convergence client. Alternatively, a contact photo added to Convegence can be viewed or modified from the Outlook Connector client.

{toc-zone}

h2. What's New in Communications Suite 6

Communications Suite 6 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. New Installer for Communication Suite

Beginning with this release of Communications Suite 6, Communications product components are installed through a new Communications Suite installer. Communications product components continue to interoperate with Java Enterprise System components. Use the Java Enterprise System installer to install Java ES components, such as Sun Java System Directory Server and Sun Java System Access Manager.

You use the Communications Suite installer, {{commpkg}}, to install, uninstall, upgrade, and backout Communications product components. The {{commpkg}} installer exists only in CLI form, but also has a silent mode of installation. No GUI form is available.

For more information on installing Communications Suite 6, see the _[Sun Java Communications Suite 6 Installation Guide|Communications Suite 6 Update 2 Installation Guide]_.

h4. Upgrading to Communications Suite 6

If you choose to upgrade to Communications 6, see the _[Communications Suite 6 Update 2 Upgrade Guide]_.

h4. System Virtualization Support

System virtualization is a technology that enables multiple operating system (OS) instances to execute independently on shared hardware. Functionally, software deployed to an OS hosted in a virtualized environment is generally unaware that the underlying platform has been virtualized. Sun performs testing of its Sun Java System products on select system virtualization and OS combinations to help validate that the Sun Java System products continue to function on properly sized and configured virtualized environments as they do on non-virtualized systems.

Communications Suite supports the VMware container (VMware ESX Server 3). As support for other virtulization platforms (LDOMs, xVM Server, etc.) becomes available we will update this document.

For information about Sun support for Sun Java System products in virtualized environments, see http://docs.sun.com/doc/820-4651.

{toc-zone}
{anchor:WhatsNewCommCenter}

h2. What's New in Convergence 1.0

Convergence is Sun's next-generation web client for email, calendar, address book, and instant messaging. It provides a rich and highly interactive user experience through compelling integration of the different communication services.

The following sections list new features available in the Convergence 1.0 initial release. Additional features are planned for release in upcoming versions.

h3. General

* Highly customizable user interface
* Drag-n-drop of items, for example, dragging and dropping messages between folders
* Drag and resize user interface panels
* Quick/advanced search in mail
* Localized user interface in Spanish, French, and Japanese
* Context-sensitive actions (for some components; these will become available for additional components in future releases)

h3. Mail

* Typical email functionality
* Auto-completion of email addresses
* Rich text editing
* Server-based mail filters
* Mark as spam
* Vacation/out of office messages

h3. Calendar

* Typical calendar functionality
* Event and task management
* Multiple calendars and calendar overlay
* Calendar views: day, week, month

h3. Address Book

* Common address book
* Create and manage contacts
* Import or export contacts

h3. Instant Messaging

* Presence management
* Buddy list

{anchor:WhatsNewCalSvr}

h2. What's New in Calendar Server 6.3

Calendar Server 6.3 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Passwords Removed From Calendar Server Configuration Files and Obfuscated

In the past, the Calendar Server configuration file stored some passwords in clear text. Though the {{ics.conf}} file has read permission restrictions, the passwords could be visible to someone else when the administrator edits the configuration file. In Calendar Server 6.3, the passwords have been moved to another file and obfuscated by base 64 encoding them. The base 64 encoding prevents someone from accidentally seeing the passwords. You must still protect the file with read permission restrictions, and keep the file secure so that no unauthorized user can get to it, to keep the passwords secure.

If you are installing Calendar Server for the first time, the configuration program encodes the passwords that you create during the configuration process, and stores them in a separate password configuration file.

If you are upgrading your existing Calendar Server software to the Calendar Server 6.3 version, the configuration program encodes the existing passwords found in the {{ics.conf}} file, and moves them to the password configuration file.

In both cases, the configuration program also adds a new {{ics.conf}} parameter to indicate the location of the password file, as shown in the following example:

{{local.passwordfile="/etc/opt/SUNWics5/config/icspassword.conf"}}

Do not change this configuration parameter.

Due to this change, the following configuration parameters have been moved out of the {{ics.conf}} file:
* {{local.authldapbindcred}}
* {{local.enduseradmincred}}
* {{local.lookupldapbindcred}}
* {{service.siteadmin.cred}}

{info:title=Note}
The LDAP bind passwords that are generated by the configurator are re-generated each time you run the configurator, once they are moved out of the {{ics.conf}} file.
{info}

h4. Support in Calendar Server for Service Management Framework

Calendar Server 6.3 supports the Service Management Framework (SMF), for stopping and starting Calendar Server. For more information, see [CommSuite:Using Service Management Framework with Calendar Server].

{toc-zone}

{anchor:WhatsNewCommCenter}



h2. What's New in Messaging Server 7.0

Messaging Server 7.0 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Messenger Express Interface Removed

The Messenger Express GUI has been deprecated and is being removed from the Messaging Server 7.0 release. For an in-place upgrade to Messaging Server 7.0, the installation process removes the existing, pre-Messaging Server 7.0 Messaging Express files, and saves the files in a backup directory. If you upgrade to Messaging Server 7.0 and then downgrade to a previous release, the downgrade process does not automatically restore the Messaging Express files. You would need to manually restore the Messenger Express files from the backup directory.

The default port for the {{mshttpd}} daemon (used by Messenger Express) has been changed to a well-known IANA-registered port, 8990. You also need to make a corresponding port change to your Communications Express configuration. The Messaging Server 6 release's default for the {{mshttpd}} port is 80, which is commonly used for web servers. Moving {{mshttpd}} to a different port signifies the removal of the web-page serving function of {{mshttpd}} (that is, Messenger Express).

Browsers will no longer connect to the {{mshttpd}} daemon as an HTTP web server, as {{mshttpd}} will no longer serve HTTP directed to end users, but instead will serve mail services to Convergence and Communications Express.

h4. {{moveuser}} Support for Mail Servers That Do Not Support the NAMESPACE command.

Additional flags for the {{moveuser}} command provide support for moving user when the source mail server does not support the IMAP {{NAMESPACE}} command. See [CommSuite:moveuser].

h4. Messaging Server Message Store Supports Very Large Mailboxes

In Messaging Server 5 and 6, the {{store.idx}} files, which contain the message index and cache records, were limited to 2 Gbytes in size. Because of this limit on the {{store.idx}} file, the size of an actual mailbox was limited to about 1 million messages on average, depending on the header size and the complexity of the messages. Messaging Server 7.0 increases the number of messages a mailbox can contain to 4,294,967,295, creating in Messaging Server terms, a "very large" mailbox.

New {{configutil}} parameters have been added to Messaging Server to manage very large mailboxes. For more information, see [CommSuite:Administering Very Large Mailboxes].

h4. Message Store Maintenance Queue

In addition to support for large mailboxes, the way in which the message store purges mailboxes has changed, making the process more efficient when dealing with a large mailbox. In Messaging Server 7.0, only the index file is purged when a mailbox is expunged. The purging of cache records is deferred until the amount of expunged data has exceeded a configurable limit. In addition, the message store uses a maintenance queue to schedule mailbox purge and repair tasks. Mailbox corruptions detected by the message store are also queued for repair automatically. You use the {{impurge}} command to purge unused cache records and message files in mailboxes.

For more information, see [CommSuite:Message Store Maintenance Queue].

h4. Support for Lemonade Profile 1 and Future Release

Messaging Server 7.0 supports Lemonade Profile 1, defined by [http://www.ietf.org/rfc/rfc4550.txt]. Among other features, this includes an extension to the SMTP submission protocol for a client to indicate a future time for the message to be released for delivery. This extension permits a client to use server-based storage for a message that should be held in queue until an appointed time in the future. Clients that do not have local storage or are otherwise unable to release a message for delivery at an appointed time can leverage this functionality. In addition, you can use this functionality to send announcements to be read at the beginning of a work day, to send birthday greetings a day or so ahead, or to create a lightweight personal reminder service.

For more information, see [http://www.ietf.org/rfc/rfc4865.txt]. For more information on using Lemonade with Messaging Server, see [CommSuite:Messaging Server Lemonade Profile 1 Support].

h4. Support for BURL

Messaging Server 7.0 supports the BURL command, which extends the SMTP submission profile by adding a new command to fetch submission data from an IMAP server. This permits a mail client to inject content from an IMAP server into the SMTP infrastructure without downloading it to the client and uploading it back to the server. Thus, you could forward an email message without first downloading it to the client.

For more information, see [http://www.ietf.org/rfc/rfc4468.txt].

h4. IMAP URLAUTH Support

Messaging Server 7.0 supports the URLAUTH extension to IMAP and the IMAP URL Scheme (IMAPURL). This extension provides a means by which an IMAP client can use URLs carrying authorization to access limited message data on the IMAP server. An IMAP server that supports this extension indicates this with a capability name of "URLAUTH."

For more information, see [http://www.ietf.org/rfc/rfc4467.txt].

h4. IMAP CATENATE Support

Messaging Server 7.0 supports the CATENATE extension to IMAP, which extends the APPEND command to allow clients to create messages on the IMAP server that may contain a combination of new data along with parts of (or entire) messages already on the server. Using this extension, the client can catenate parts of an already existing message onto a new message without having to first download the data and then upload it back to the server.

For more information, see [http://www.ietf.org/rfc/rfc4469.txt].

{excerpt:hidden=true}
h4. IMAP Conditional Store Operation Support

Messaging Server 7.0 supports IMAP Conditional Store Operations (CONDSTORE). IMAP CONDSTORE enables clients to coordinate changes to a common IMAP mailbox, for example, when multiple users are accessing shared mailboxes. The Conditional Store facility provides a protected update mechanism for message state information that can detect and resolve conflicts between multiple writing mail clients. The Conditional Store facility also allows a client to quickly resynchronize mailbox flag changes.

For more information, see [http://www.ietf.org/rfc/rfc4551.txt].
{excerpt}

h4. IMAP ANNOTATE Support

Messaging Server 7.0 supports the ANNOTATE extension to IMAP, which permits clients and servers to maintain "meta data" for messages, or individual message parts, stored in a mailbox on the server. For example, you could use IMAP ANNOTATE to attach comments and other useful information to a message, or to attach annotations to specific parts of a message, marking them as seen or important, or a comment added.

For more information, see [http://www.ietf.org/rfc/rfc5257.txt].

h4. Message Store Database Rolling Backup

The message store has been enhanced to continuously recover archived log files into an up-to-date backup copy of the message store database. If the actual database becomes unusable, then the message store will automatically use this backup database. Having an up-to-date database backup provides the next level of recovery and stability for the message store.

h4. Messaging Server and Service Tags

[Sun Service Tags|https://sunconnection.sun.com/FAQ/sc_faq.html] are used solely to identify Sun products to Sun. Sun uses service tag information to better support you. Registration data is only collected when your system administrator requests gear discovery. Messaging Server 7.0 enables you to use the Service Tag Facility on Solaris OS 10.

For more information, see [CommSuite:Using Service Tags with Messaging Server].

h4. Additional Support for Java Enterprise System Monitoring Framework

Additional integration of Messaging Server and Java Enterprise System Monitoring Framework (JESMF) has been added to this release. JESMF provides information on the length of time for authentication, message delivery, the number of instant messages sent through the service, and other statistics.

For information on the Sun Java Enterprise System Monitoring Framework, see: [_Sun Java Enterprise System 5 Monitoring Guide_|http://docs.sun.com/app/docs/doc/819-5081].

h4. Support in Messaging Server for Service Management Framework

Messaging Server 7.0 supports the Service Management Framework (SMF), for stopping and starting Messaging Server. For more information, see [CommSuite:Using Service Management Framework with Messaging Server].

h4. Remote Administration

The self-contained remote administration shell (via the {{msgadm}} command) in Messaging Server 7.0 is intended to make management more appliance-like. For more information, see [CommSuite:Administering Messaging Server Remotely].

h4. Message Store Load Throttling

Occasionally, the message store DB experiences contention related performance issues when under very heavy activity. To ensure a graceful degradation of store performance under increased load, Messaging Server 7.0 throttles DB load based on a new contention metric. This metric is used to throttle (shrink pool) or accelerate (grow pool) DB operations to an optional DB load metric value. Note that storage I/O bandwidth is another contended resource that might require throttling. Messaging Server 6.3 already throttles, based on storage capacity.

h4. Moving Messaging Server Users From One Mailhost to Another
The {{rehostuser}} utility enables you to move a Messaging Server user's mail from one mailhost or partition to another.

h4. Message Store reconstruct Command Revised

The message store {{reconstruct}} command has been modified to handle new file formats in Messaging Server 7.0. In addition, changes have been made to {{reconstruct}} to address multiple CRs and RFEs, as well as how to perform to repair and recovery.

The {{reconstruct}} command was originally designed to address folders and users in a breadth first manner, one database at a time. (This approach got the message store running, but each user was not completely repaired.) Today, the store's self-repair techniques can already get the store running. Thus, it is now more appropriate for {{reconstruct}} to also have the capability to address a single user completely. This approach also moves towards automatic and complete repair of individual users.

h4. imcheck Enhancements

The following options have been added to the {{imcheck}} command:

* Print database statistics:\\
\\ {{imcheck -s}} _subsystem..._\\
\\where subsystem is: {{mpool}}, {{lock}}, {{log}}, or {{txn}}\\
\\If subsystem is not specified, all available information is printed.

* Print mailbox data:\\
\\ {{imcheck -x}} _dir_\\
\\ -x _dir_ prints metadata for the mailbox under the specified directory.

* Print maintenance queue:\\
\\ {{imcheck}} -q

h4. Delivering Bulk Mail to All Users

The {{deliver}} command has been enhanced to include a {{-p}} option to specify a user ID pattern. For example, to deliver a message to all users in the message store, use this command:

{noformat}
deliver -p "*" < msg_file
{noformat}

For more information on the {{deliver}} command, see _[Sun Java System Messaging Server 6.3 Administration Reference|http://docs.sun.com/app/docs/doc/819-4429/acmbc?a=view]_.

h4. Restoring Mailboxes to a Specific Partition

The following {{-P}} _partition_ option has been added to the {{imsrestore}} command, to specify the restored partition.

|{{-P}} _partition_|Restores all mailboxes to the specified partition (ignore {{-p}} and {{mailMessageStore}})|

h4. Compact WMAP
Messaging Server JavaScript client code has been improved and optimized. This results in bandwidth savings, simpler code, and better client responsiveness.

h4. Changes to the configutil Command

The initial configuration utility no longer generates initial settings for most {{configutil}} options. Running the {{configutil}} command with no arguments lists all options with settings (initial or otherwise). Due to the reduced number of initial settings, {{configutil}} with no arguments now lists far fewer options than in the past. The {{configutil -H}} command lists all documented {{configutil}} options along with their default and current values. The {{configutil -o}} command now returns either the current value, or if no value is currently set, the default value.

The following {{configutil}} parameter defaults have changed from Messaging Server 6.3. For more information, see [configutil Parameters|CommSuite:Messaging Server Configuration].
|{{local.mfagent.connection_stats_interval}}|Set how often, in seconds, to refresh the connection statistics.|
|{{local.mfagent.debug}}|Set a bit mask for various types of debugging in the mfagent.|
|{{local.mfagent.host_stats_interval}}|Set how often, in seconds, to refresh the hosts statistics.|
|{{local.mfagent.listenaddr}}|Sets the bind address for the mfagent.|
|{{local.mfagent.max_report_hosts}}|Sets the maximum number of hosts to be reported on for channel queues. Do not set higher than 12.|
|{{local.mfagent.monitor_level}}|Sets the level of transaction monitoring. The range is 0 (least) to 7 (most).|
|{{local.mfagent.oldest_message_update}}|Sets the frequency of updating the oldest message info. the oldest message info is updated every nth time the connection stats are updated, n being this parameter.|
|{{local.mfagent.port}}|Sets the port on which the mfagent listens.|
|{{local.mfagent.secret}}|The shared secret used to authenticate connections to the mfagent.|
|{{local.mfagent.timeout}}|Timeout for how long components will try to connect to the mfagent.|
|{{local.purge.enable}}|Enable {{purge}} server on {{start-msg}} startup.|
|{{local.schedule.snapshot}}|{{imdbverify}} snapshot and verify, enabled with {{local.schedule.snapshot.enable}}. {{imdbverify}} will take a snapshot backup copy of the database and verify it for use during automatic recovery.|
|{{local.schedule.snapshot.enable}}|Whether the snapshot / verify task should be scheduled.|
|{{local.store.deadlockaggressive}}|A non zero integer N indicates aggressive deadlock resolution, combined by delaying transaction retries by N seconds.|
|{{local.store.rollingdbbackup}}|Controls whether rolling store database backups are made. (yes/no).|
|{{logfile.tcp_lmtp_service.buffersize}}|Size of LMTP log buffers in bytes.|
|{{logfile.tcp_lmtp_service.expirytime}}|Maximum time an LMTP log file is kept (in seconds).|
|{{logfile.tcp_lmtp_service.flushinterval}}|Time interval for flushing buffers to LMTP log files (in seconds).|
|{{logfile.tcp_lmtp_service.logdir}}|Directory path for LMTP log files.|
|{{logfile.tcp_lmtp_service.loglevel}}|Specify an LMTP log level. One of Nolog, Emergency, Alert, Critical, Error, Warning, Notice, Information, or Debug.|
|{{logfile.tcp_lmtp_service.logtype}}|Ignored. Set to either NscpLog or syslog.|
|{{logfile.tcp_lmtp_service.maxlogfiles}}|Maximum number of LMTP log files.|
|{{logfile.tcp_lmtp_service.maxlogfilesize}}|Maximum size (bytes) of each LMTP log file.|
|{{logfile.tcp_lmtp_service.maxlogsize}}|Maximum size of all LMTP log files.|
|{{logfile.tcp_lmtp_service.minfreediskspace}}|Minimum amount of free disk space (bytes) that must be available for LMTP logging.|
|{{logfile.tcp_lmtp_service.rollovertime}}|The frequency in which to rotate the LMTP log file (in seconds).|
|{{logfile.tcp_lmtp_service.syslogfacility}}|Specifies whether or not LMTP logging goes to syslog. The values can be user, mail, daemon, local0 to local7, or none. If the value is set, messages are logged to the syslog facility corresponding to the set value and all other log file service options are ignored.|
|{{service.http.smtptls}}|Whether to use TLS for SMTP connections.|
|{{service.imap.ensidle}}|If set, use ENS for imkill without idle, if unset, use JMQ.|
|{{service.imap.idle}}|Sets values for {{local.store.notifyplugin}} and {{local.store.notifyplugin.\*.\*.enable}} for IMAP IDLE to work.|
|{{service.imap.submituser}}|Store userid used by the MTA when resolving submit IMAP URLs in BURL commands.|
|{{service.imap.withinresolution}}|Interval (in minutes) between recalculations of Contexts involving the search options YOUNGER or OLDER. The value 0 means 30 seconds.|
|{{service.imap.capability.acl}}|Advertise the ACL imap extension.|
|{{service.imap.capability.annotate}}|Advertise the ANNOTATE-EXPERIMENT-1 imap extension.|
|{{service.imap.capability.binary}}|Advertise the BINARY imap extension.|
|{{service.imap.capability.catenate}}|Advertise the CATENATE imap extension.|
|{{service.imap.capability.children}}|Advertise the CHILDREN imap extension.|
|{{service.imap.capability.context}}|Advertise the CONTEXT imap extension.|
|{{service.imap.capability.esearch}}|Advertise the ESEARCH imap extension.|
|{{service.imap.capability.idle}}|Advertise the IDLE imap extension.|
|{{service.imap.capability.imap4}}|When set to yes, advertise the IMAP4 capability. The default is yes if {{local.obsoleteimap}} is set.|
|{{service.imap.capability.imap4rev1}}|When set to yes, advertise the IMAP4rev1 capability. The default is yes if {{local.obsoleteimap}} is set.|
|{{service.imap.capability.language}}|Advertise the LANGUAGE imap extension.|
|{{service.imap.capability.literal_plus}}|Advertise the LITERAL+ imap extension.|
|{{service.imap.capability.namespace}}|Advertise the NAMESPACE imap extension.|
|{{service.imap.capability.qresync}}|Advertise the QRESYNC imap extension.|
|{{service.imap.capability.quota}}|Advertise the QUOTA imap extension.|
|{{service.imap.capability.sort}}|Advertise the SORT imap extension.|
|{{service.imap.capability.starttls}}|Advertise the STARTTLS imap extension.|
|{{service.imap.capability.thread_references}}|Advertise the THREAD=REFERENCES imap extension.|
|{{service.imap.capability.thread_subject}}|Advertise the THREAD=ORDEREDSUBJECT imap extension.|
|{{service.imap.capability.uidplus}}|Advertise the UIDPLUS imap extension.|
|{{service.imap.capability.unselect}}|Advertise the UNSELECT imap extension.|
|{{service.imap.capability.urlauth}}|Advertise the URLAUTH imap extension.|
|{{service.imap.capability.within}}|Advertise the WITHIN imap extension.|
|{{service.imap.capability.x_annotatemore}}|Advertise the X-ANNOTATEMORE imap extension.|
|{{service.imap.capability.x_netscape}}|Advertise the X-NETSCAPE imap extension.|
|{{service.imap.capability.x_sun_imap}}|Advertise the X-SUN-IMAP imap extension.|
|{{service.imap.capability.x_sun_sort}}|Advertise the X-SUN-SORT imap extension.|
|{{service.imap.capability.x_unauthenticate}}|Advertise the X-UNAUTHENTICATE imap extension.|
|{{service.imap.capability.xrefresh}}|Advertise the XREFRESH imap extension.|
|{{service.imap.capability.xsender}}|Advertise the XSENDER imap extension.|
|{{service.imap.capability.xserverinfo}}|Advertise the XSERVERINFO imap extension.|
|{{service.imap.capability.xum1}}|Advertise the XUM1 imap extension.|
|{{service.imap.idle.jmqhost}}|The name or address of the host where the JMQ broker is to be found.|
|{{service.imap.idle.jmqpassword}}|The JMQ password used to subscribe to messaging events.|
|{{service.imap.idle.jmqport}}|The port number the JMQ broker is listening on.|
|{{service.imap.idle.jmqtopic}}|The JMQ topic to which mail events are published.|
|{{service.imap.idle.jmquserid}}|The JMQ userid used to subscribe to messaging events.|
|{{store.autorepair}}|Repair damaged mailboxes automatically.|
|{{store.mailboxexpungesize}}|Size (in bytes) of expired or expunged message before purge will permanently remove it. Minimum value is 1048576.|
|{{store.maxcachefilesize}}|Maximum cache file size (in bytes). A new cache file is created when the current cache file size has exceeded this limit. Minimum value is 1048576.|
|{{store.purge.loglevel}}|Specify a log level: 0: no log. 1: basic log. 2: verbose log.|
|{{store.purge.maxthreads}}|Maximum number of threads.|

||*Parameter*||*6.3 Default*||*7.0 Default*||
|{{local.autorestart}}|no|yes|
|{{local.ens.enable}}|&lt;ensEnable&gt;|0|
|{{local.store.listrecover}}|NULL|TestPartitionInsertFull|
|{{service.http.port}}|80|8990|
|{{service.http.sslport}}|443|8991|

Running {{configutil -h}} displays two new options ({{-x}} and {{-a}}). These options are for a future enhancement that is not active for Messaging Server 7.0. These options do not affect the current configuration other than to issue a warning that they are ignored.

h4. Sieve Filter Implementation
See [http://msg.wikidoc.info/index.php/Sieve_Implementation].

h4. Vacation Replies Can Be Sent to Forwarded Messages
Messaging Server 7.0 can now generate {{:addresses}} arguments to Sieve vacation using an LDAP autoreply attribute. The new MTA option {{LDAP_AUTOREPLY_ADDRESSES}} provides the name of the attribute to use. This option has no value by default. The attribute can be multivalued, with each value specifying a separate address to pass to the {{:addresses}} vacation parameter. The {{:addresses}} argument to Sieve vacation specifies other addresses which will be deemed to be the the same as the recipient. This allows vacation autoreply to be sent even when none of the header recipient addresses of the message match any valid address of the user. The attribute will need to be added to the directory server schema, this option specified in option.dat, and the attribute values added to users LDAP objects.

h4. Changes to the {{nameservers}} channel keyword

When nameserver lookups are being performed, that is, unless the {{nsswitch.conf}} file selects no use of nameservers, then prior to Messaging Server 7.0 the {{nameservers}} channel keyword may be used to specify a list of nameservers to consult rather than consulting the TCP/IP stack's own choice of nameservers. This would affect the SMTP server and client and LMTP client, but not the LMTP server (which, if it needs to do any lookups, always relies on the TCP/IP stack's own choice of nameservers). Furthermore, as of Messaging Server 7.0, the {{nameservers}} keyword only affects MX record lookups, with all other lookups using the TCP/IP stack's choice of nameservers regardless of any {{nameservers}} keyword setting.

{toc-zone}

h2. What's New in Instant Messaging 7.3

Instant Messaging 7.3 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Support for LDAP Failover
Support for LDAP failover in Instant Messaging 7.3 enables you to configure the Instant Messaging server to have multiple LDAP servers as back-end storage. If one LDAP server becomes unavailable, the Instant Messaging server is then able to fail over to another LDAP server.

LDAP failover works on a multi-master replication setup of LDAP servers. All the LDAP servers in the settings are masters and have permission to read and write data. The Instant Messaging server uses only one server at a time but fails over to another LDAP server when the current server becomes unavailable. The other LDAP server is expected to be in sync with the current server as far as data is concerned.

For more information, see the [CommSuite:Sun Java System Instant Messaging Administration Guide].

h4. Support for Voice Chat and Client-to-Client Chat

The previous releases of Instant Messaging did not have any audio capability. Instant Messaging 7.3 provides the capability for Instant Messaging users to talk to each other using PC-based audio hardware. The Instant Messaging client uses the Instant Messaging Server to only set up the call. Afterwards, the audio streams travel in a peer-to-peer fashion.

To enable voice chat, select the "Enable Audio" checkbox when deploying the Instant Messaging Client Resources.

h4. Support for Instant Messaging and Presence Service Protocol

Instant Messaging 7.3 supports Instant Messaging and Presence Service (IMPS) protocol, which enables mobile instant messaging and presence services. You use IMPS to exchange messages and presence information between mobile devices, mobile services and Internet-based instant messaging services. IMPS access is provided via a web-application in the Instant Messaging server. The IMPS web-application can be deployed to a supported web container using the Instant Messaging configuration utility.

For more information, see the [CommSuite:Sun Java System Instant Messaging Administration Guide].

h4. Support for Service Management Framework
Instant Messaging 7.3 supports the Service Management Framework (SMF), for stopping and starting Instant Messaging. On supported platforms, an SMF service is registered when you install Instant Messaging server. You can use either the {{svcadm}} command or the Instant Messaging {{imadmin}} utility to start and stop Instant Messaging processes.

h4. Side-by-side Upgrade Capability

Instant Messaging 7.3 enables you to perform a side-by-side upgrade. That is, the upgrade process supports a coexistence approach on the host being upgraded.

h4. Hosted Domain Support with Schema 1 and Schema 2

Instant Messaging 7.3 enables support for hosted domain using LDAP specific tree without using Identity.

For more information, see the [CommSuite:Sun Java System Instant Messaging Administration Guide].

h4. Java Messaging Service Support for Calendar Server Alerts

Instant Messaging 7.3 uses Java Message Queue as the calendar agent for calendar reminders. In previous releases, the calendar agent was using ENS, which will be deprecated in a future release.

For more information, see the [CommSuite:Sun Java System Instant Messaging Administration Guide].

h4. Property Store Migration

Instant Messaging 7.3 provides property store migration that enables migration to and from the file propstore and from and to the LDAP propstore. The destination store must have the appropriate entries users configured. This migration does not create users; it only migrates the user data. It currently does not support mixed case entries, and flags them as errors.

For more information, see the [CommSuite:Sun Java System Instant Messaging Administration Guide].

h4. Support for the {{migratecert}} Command

Instant Messaging 7.3 enables migration of private key and Multiplexor certificate from the NSS database to JKS. A migration utility has been added for this purpose in the {{imadmin}} command.

Instant Messaging 7.3 no longer supports SSL through the Multiplexor using NSS-based certificates, however, you can now migrate the existing certificates from NSS store to JKS using the {{migratecert}} command.

For more information, see the [CommSuite:Sun Java System Instant Messaging Administration Guide].

{toc-zone}

h2. What's New in Delegated Administrator 6.4

The Delegated Administrator 6.4 released with Communications Suite 6 does not include any new features since the release of Delegated Administrator 6.4 with Communications Suite 5. See [Problems Fixed in This Release of Delegated Administrator|CommSuite6:Delegated Administrator 6.4 Release Notes#DelegatedAdministrator6.4ReleaseNotes-ProblemsFixedinThisReleaseofDelegatedAdministrator] for a list of fixes to this release.

The following minor features were introduced in Delegated Administrator 6.4 with the Communications Suite 6 release:

* [Support for Sun Java System Application Server 9.x|Delegated Administrator 6.4 Release Notes#Sun Java System Software]

{anchor:WhatsNewCommExp}

h2. What's New in Communications Express 6.3

Communications Express 6.3 includes the following changes:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. New Property (uwc.loginseparator) Added to {{uwcauth.properties}}

This property is used to configure authentication separator while logging in to Communications Express 6.3. Login separator 'is' or 'are' character(s) are used to separate the userID and domain. For example, the login name could be user@domain.com.

The default value for this property is {{@}}.

See [Problems Fixed in This Release of Communications Express|CommSuite6U1:Communications Express 6.3 Release Notes#Problems Fixed in This Release of Communications Express] for a list of fixes to this release.

{toc-zone}

h2. What's New in Connector for Outlook 7.3

Connector for Outlook 7.3 includes the following changes and new features:
{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. Support for Large PST Files

Connector for Outlook 7.3 supports a larger PST file (20 Gbytes), which was introduced in Microsoft Outlook 2003. In the past, the PST file was limited to 2 Gbytes of data. Users using Microsoft Outlook 2003 and Microsoft Outlook 2007 will now use the large PST file as their local store for Connector for Outlook.

h4. Service Tags and Connector for Outlook

Sun Service Tags are used solely to identify Sun products to Sun. Sun uses service tag information to better support you. Registration data is only collected when your system administrator requests gear discovery. For more information, see [http://servicetags.central].

h4. Support for Outlook 2007

Connector for Outlook 7.3 now supports Microsoft Outlook 2007.

h4. Support for Microsoft Vista

Connector for Outlook 7.3 now supports Microsoft's Windows Vista operating system.

h4. Ability to Disable Save Password Field

Connector for Outlook 7.3 now supports a security feature that enables administrators to restrict users from saving their passwords in profile.

h4. New Deployment Tool Path

To conform with Sun's products installation paths, Connector for Outlook deployment tool now uses the following path:
{noformat}
Start -> Programs -> Sun Microsystems -> Sun Java System Connector Deployment
{noformat}

h4. Customizing the Location of the Personal Store (.pst) File

By default, Connector for Outlook 7.3 stores pst files at {{C:\Documents and Settings\_username_\Local Settings\Sun\Outlook Connector}}. This feature enables administrators to decide the location of pst files on a user's machine.

h4. Polling in Address Book

Connector for Outlook 7.3 enables you to set an option to run polling at certain time intervals. This feature ensures you keep your address book updated without any manual intervention.

h4. Ability to Customize LDAP Attribute Mapping and GAL Display Order

Outlook Connector maps the LDAP attributes to the corresponding display items in Outlook. You can now customize the LDAP attribute mapping and GAL display order from the Deployment Program.
{toc-zone}