Support for the following features may be eliminated in a future release or have already been removed in this release:
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. Both Messenger Express and Calendar Express will be removed from the product in the next major release.
This deprecation also includes the deprecation of the Messenger Express Mail Filter User Interface (msg-svr-base /SUNWmsgmf/MailFilter.war ).
The following bugs affect the deprecated Messenger Express product:
The Up and Down buttons removed.
The Up and Down buttons used to specify the ordering of your filters have been removed.
Problems may be seen in Messenger Express on Internet Explorer 6 when proxy server setting is used.
Workaround: Enable or disable “auto-detection” option in Internet Explorer’s encoding menu. Use direct connection or switch to different proxy server.
Feature removed from the Advanced Mail Filter Conditions window.
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).
Localized Messenger Express does not merge some of the folders created by Outlook Express.
It is sometimes desired that the default “Sent” folder in Messenger Express be replaced by the “Sent Items” folder created by Outlook Express, hence all the messages sent by both client are copied to the “Sent Items” folder. This does not work with Japanese localization.
Workaround:
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.
Directory Server is exhibiting correct behavior. Due to a problem in Netscape Directory Server 4.x, you are able to enter multiple email IDs.
The Sun Java System Administration Console has been removed from the Messaging Server product.
Administration functions should be performed through the Messaging Server command-line interfaces or configuration files. References in the documentation to using the console haven't yet been corrected.
When clients connect via IMAP, POP or SMTP to the Messaging Server, they must use a SASL (RFC 2222) authentication mechanism or a simple password to prove their identity to the server. When the LDAP directory is configured to store user passwords in the clear, all user passwords are migrated to this format and the sasl.default.ldap.has_ plain_passwords option is set on the Messaging Server, then three additional authentication mechanisms are enabled: APOP, CRAM-MD5 and DIGEST-MD5. All three of these mechanisms transmit a one-way encoding of the password over the wire rather than the password itself. Due to its limited deployment and complexity, the DIGEST-MD5 mechanism is deprecated leaving only the APOP and CRAM-MD5 mechanisms.
The LMTP native channel has been deprecated and will be removed in a future release.
The Messenger Express Multiplexor has been removed in favor of the Webmail Server. See: Webmail Server Supports IMAP.
This command has been deprecated. Use imsimta cnbuild in Sun Java System Messaging Server 6.3 Administration Reference and imsimta restart in Sun Java System Messaging Server 6.3 Administration Reference instead, as appropriate.
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.
See start-msg in Sun Java System Messaging Server 6.3 Administration Reference and stop-msg in Sun Java System Messaging Server 6.3 Administration Reference for more information.
The optional SECTION option for the INSTANCENAME option of the ServiceList MMP configuration parameter is deprecated and will be removed in a future release.
MTA access to database files and the imsimta tools to manipulate MTA database files are deprecated.
Netscape browser support will be removed at a future date.
Red Hat Linux 3 platform support has been deprecated in this release and be removed in a future release. Communications Suite 5 continues to be supported on Red Hat Linux 4.
In this release, there are two notification services for event notifications and alarms: Sun Java System Message Queue (JMQ) and Event Notification Service (ENS). In a future release, the Communications Suite products will use JMQ exclusively and ENS will be deprecated. However, for this release, Messaging Server, Calendar Server, and Instant Messaging still have internal dependencies to ENS; therefore, you can continue to use ENS.
For this release, the Messaging Server IMAP IDLE feature requires the use of ENS. Messaging Server has no other dependencies on ENS. If you do not use IMAP IDLE, you can use JMQ exclusively for event notifications.
If you want to use IMAP IDLE, you must configure an ENS notification plug-in. You can also use JMQ for message notifications by configuring a JMQ notification plug-in. (Messaging Server allows you to configure multiple notification plug-ins.
The configutil parameters listed in Table 3–2 are obsolete and have been removed from the Messaging Server product.
If Messaging Server is upgraded from an earlier release to Messaging Server 6.3, the parameters listed in Table 3–2 are deleted from the configuration after upgrade. Before upgrading, Sun recommends that you save the configutil output to a file.
Parameter |
Comment |
---|---|
Removed in Messaging Server 6.0. No replacement. |
|
Use local.ssldbpath and local.ssldbprefix instead. |
|
Use local.ssldbpath and local.ssldbprefix instead. |
|
No longer relevant with SSL v2 support obsoleted (as of Messaging Server 6.0). |
|
No longer relevant with SSL v2 support obsoleted (as of Messaging Server 6.0). |
|
No longer relevant with SSL v2 support obsoleted (as of Messaging Server 6.0). SSL v3 is now always enabled. |
|
Removed in Messaging Server 6.0. No replacement. |
|
Removed in Messaging Server 6.0. Use service.*.sessiontimeout instead. |
|
Removed in Messaging Server 6.0. SSL now always asks for client cert if there is a valid certmap.conf and a valid CA for client certs in the cert database. |
|
Removed in Messaging Server 6.0. Use service.*.sessiontimeout instead. |
|
Removed in Messaging Server 6.0. No replacement. |
|
Removed in Messaging Server 6.0. Use encryption.rsa.nssslpersonalityssl and local.*.sslnicknames instead. The token name can be provided as a prefix to the SSL nickname: for example, token-name:nick-name . |
|
Never used. |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
Removed in Messaging Server 6.2. Use alarm.serverresponse.msgalarmstatinterval instead. |
|
Never used. SSO will be enabled so long as local.webmail.sso.amnamingurl and related parameters are defined. |
|
Use local.enduseradmincred instead. |
|
Use local.enduseradmindn instead. |
|
No longer relevant with dirsync obsoleted (as of Messaging Server 6.0). |
|
Use the LDAP_TIMEOUT MTA option instead. |
|
No longer relevant with dirsync obsoleted (as of Messaging Server 6.0). |
|
No longer relevant with dirsync obsoleted (as of Messaging Server 6.0). |
|
No longer relevant with dirsync obsoleted (as of Messaging Server 6.0). |
|
No longer relevant with dirsync obsoleted (as of Messaging Server 6.0). |
|
Use the LOG_MESSAGES_SYSLOG MTA option instead. |
|
No longer relevant with dirsync obsoleted (as of Messaging Server 6.0). |
|
No longer relevant with dirsync obsoleted (as of Messaging Server 6.0). |
|
No longer relevant with dirsync obsoleted (as of Messaging Server 6.0). |
|
No longer relevant with dirsync obsoleted (as of Messaging Server 6.0). |
|
No longer relevant with dirsync obsoleted (as of Messaging Server 6.0). |
|
No longer relevant with dirsync obsoleted (as of Messaging Server 6.0). |
|
Use the DOMAIN_MATCH_URL MTA option instead. |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
Removed in Messaging Server 6.2. No replacement. |
|
No longer necessary. |
|
MEM is obsoleted now that webmail communicates with the store via IMAP (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
Use local.snmp.servertimeout instead. |
|
Use local.schedule.expire instead. |
|
Use local.store.maxlog instead. |
|
Use local.store.notifyplugin.*.deletemsg.enable instead. |
|
Use local.store.notifyplugin.*.debuglevel instead. |
|
Use local.store.notifyplugin.*.maxbodysize instead. |
|
Use local.store.notifyplugin.*.maxheadersize instead. |
|
Use local.store.notifyplugin.*.jmqhost instead. |
|
Use local.store.notifyplugin.*.jmqport instead. |
|
Use local.store.notifyplugin.*.jmqpwd instead. |
|
Use local.store.notifyplugin.*.jmqtopic instead. |
|
Use local.store.notifyplugin.*.jmquser instead. |
|
Use local.store.notifyplugin.*.loguser.enable instead. |
|
Use local.store.notifyplugin.*.newmsg.enable instead. |
|
Use local.store.notifyplugin.*.noneinbox.enable instead. |
|
Use local.store.notifyplugin.*.purgemsg.enable instead. |
|
Use local.store.notifyplugin.*.readmsg.enable instead. |
|
Use local.store.notifyplugin.*.updatemsg.enable instead. |
|
Never used. |
|
Never used. |
|
Use sasl.default.ldap.has_plain_passwords instead. |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
Use local.webmail.cert.enable instead. |
|
Use local.webmail.cert.port instead. |
|
Use local.service.http.ims5compat if necessary. |
|
Calendar Server parameter. Not used in Messaging Server. |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3). |
|
Use sasl.default.auto_transition instead. |
|
Use the LDAP attribute mailAllowedServiceAccess instead. |
|
Use the LDAP attribute mailAllowedServiceAccess instead. |
|
Removed in Messaging Server 5.2p2. Use service.experimentalldapmemcache instead. |
|
Removed in Messaging Server 5.0. No replacement. |
|
Removed in SIMS 4.0. No replacement. |
|
Removed when Administration Server obsoleted (as of Messaging Server 6.3). Use msgcert to manage certificate database instead. |
|
Use local.ssldbpath and local.ssldbprefix instead. |
|
Use local.ssldbpath and local.ssldbprefix instead. |
|
Use local.ssldbpath and local.ssldbprefix instead. |
|
Use msgcert request-cert instead. |
|
Use local.store.*synclevel instead. |
|
Use local.schedule.expire instead. |