Messaging Server 7.0 Release Notes

Chapter 4 Sun Java System Messaging Server 7.0 Release Notes

These Release Notes contain important information available at the time of the general release of Sun Java System Messaging Server 7.0 including:

About Messaging Server 7.0

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 reduce 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 of Messaging Server

See the Communications Suite 6 What's New document.

Deprecated and Removed Features for Messaging Server

Support for the following features may be eliminated in a future release, have already been removed in this release, or were removed in a previous release:

Messenger Express

The Messenger Express webmail interface has been removed from this release. During upgrade or migration, any existing Messenger Express files will be saved off in a backup directory and must be manually restored after downgrade. The default port for mshttpd has been changed from 80 to port 8990 to signify the removal of web page serving function of mshttpd. For an upgrade or migration, the mshttpd port will be set to the existing value.

Note

This removal also includes the removal of the Messenger Express Mail Filter User Interface (msg-svr-base /SUNWmsgmf/MailFilter.war ).

NSS Security Tools

The NSS security tools (certutil, modutil, pk12util, and ssltap are no longer distributed with Messaging Server. Instead, these tools are bundled with the new Communications Installer.

Administration Console

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.

DIGEST-MD5

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.

LMTP Native Channel

The LMTP native channel for delivery to /var/mail (tcp_lmtpn_server) has been removed in this release. LMTP is now only supported for delivery to the message store.

Messenger Express Multiplexor

The Messenger Express Multiplexor has been removed in favor of the Webmail Server. See: Webmail Server Supports IMAP.

imsimta refresh

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.

imsimta stop and imsimta start

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.

MMP Section and Instance features

The optional SECTION and INSTANCENAME features of the ServiceList MMP configuration parameter are deprecated and will be removed in a future release. These features make the MMP configuration more complex than necessary and it is believed the more commonly used virtual domain feature of the MMP provides sufficient configuration flexibility.

Direct Editing of MTA Databases

MTA access to database files and the imsimta tools to manipulate MTA database files are deprecated.

Netscape Browser Support

Netscape browser support will be removed at a future date.

Red Hat Linux 3 Support

Red Hat Linux 3 platform support has been deprecated in this release and will be removed in a future release. Communications Suite 6 continues to be supported on Red Hat Linux 4.

Event Notification Service (ENS)

In this release, there are two notification services for event notifications and alarms: Sun Java System Message Queue (JMQ) and Event Notification Service (ENS). For this release, Messaging Server, Calendar Server, and Instant Messaging still have internal dependencies to ENS. By default, ENS is not enabled in this release. To enable ENS, set local.ens.enable to 1.

Prior to Messaging Server 7, if you wanted to use IMAP IDLE, you had to configure an ENS notification plug-in. In this release you can use JMQ to provide IMAP IDLE notifications.

You can use JMQ for message notifications by configuring a JMQ notification plug-in. (Messaging Server allows you to configure multiple notification plug-ins.) To enable JMQ notifications, see "How do I enable JMQ event notifications?" on MsgServerDocWiki.

Ignored imta_tailor settings

As part of a future project to support an XML configuration, the MTA's tailor file is in the process of being deprecated. As previously documented, some options in that file should not have been edited or otherwise changed. With this release of Messaging Server, only eight options in that file are honored. All other options specified in the tailor file are ignored, even if they were set to non-default values. The eight options which are still honored are IMTA_LANG, IMTA_RETURN_PERIOD, IMTA_RETURN_CLEANUP_PERIOD, IMTA_RETURN_SPLIT_PERIOD, IMTA_TMP, IMTA_USER, IMTA_USER_USERNAME, and IMTA_WORLD_GROUP.

Obsolete configutil Parameters

The configutil parameters listed in the following table are obsolete and have been removed from the Messaging Server product.

Note

If Messaging Server is upgraded from an earlier release to Messaging Server 7.0, the parameters listed in the following table are deleted from the configuration after upgrade. Before upgrading, Sun recommends that you save the configutil output to a file.

Certain options have been removed from the configuration, specifically local.serverroot and local.installeddir.

Because you may have used these options to detect the location of the installed server, configutil has been modified always to return the current server installation directory for these options when queried. You can now only use configutil to query these options. The configutil command still permits you to set values for these names (as it allows any unrecognized option name while generating a warning), but such a value is ignored. The configutil command always returns the correct install directory when your request the value of one of these options.

Deleted configutil Parameters
Parameter Comment
alarm.msgalarmnoticetemplate Too prone to format errors, support dropped in 6.3 release.
encryption.fortezza.nssslactivation Removed in Messaging Server 6.0. No replacement.
encryption.nscertfile Use local.ssldbpath and local.ssldbprefix instead.
encryption.nskeyfile Use local.ssldbpath and local.ssldbprefix instead.
encryption.nsssl2 No longer relevant with SSL v2 support obsoleted (as of Messaging Server 6.0).
encryption.nsssl2ciphers No longer relevant with SSL v2 support obsoleted (as of Messaging Server 6.0).
encryption.nsssl3 No longer relevant with SSL v2 support obsoleted (as of Messaging Server 6.0). SSL v3 is now always enabled.
encryption.nsssl3ciphers Removed in Messaging Server 6.0. Replaced by local.ssladjustciphersuites.
encryption.nsssl3sessiontimeout Removed in Messaging Server 6.0. Use service.*.sessiontimeout instead.
encryption.nssslclientauth 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.
encryption.nssslsessiontimeout Removed in Messaging Server 6.0. Use service.*.sessiontimeout instead.
encryption.rsa.nssslactivation Removed in Messaging Server 6.0. Replaced by local.ssladjustciphersuites.
encryption.rsa.nsssltoken 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: e.g., token-name:nick-name.
gen.configversion Never used.
local.cgiexeclist No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
local.dbstat.captureinterval Removed in Messaging Server 6.2. Use alarm.serverresponse.msgalarmstatinterval instead.
local.defdomain Use service.defaultdomain instead.
local.dsame.auth.enable Never used. AM SSO will be enabled so long as local.webmail.sso.amnamingurl and related parameters are defined.
local.enduseradmincred Use local.ugldapbindcred instead.
local.enduseradmindn Use local.ugldapbinddn instead.
local.enduseradminpwd Use local.ugldapbindcred instead.
local.enduseradminuid Use local.ugldapbinddn instead.
local.imta.catchallenabled No longer relevant with dirsync obsoleted (as of Messaging Server 6.0).
local.imta.ldsearchtimeout Use the LDAP_TIMEOUT MTA option instead.
local.imta.lookupandsync No longer relevant with dirsync obsoleted (as of Messaging Server 6.0).
local.imta.lookupfallbackaddress No longer relevant with dirsync obsoleted (as of Messaging Server 6.0).
local.imta.lookupmaxnbfailed No longer relevant with dirsync obsoleted (as of Messaging Server 6.0).
local.imta.lookupreturnwhenfound No longer relevant with dirsync obsoleted (as of Messaging Server 6.0).
local.imta.nsmsglog.enable Use the LOG_MESSAGES_SYSLOG MTA option instead.
local.imta.reverseenabled No longer relevant with dirsync obsoleted (as of Messaging Server 6.0).
local.imta.scope No longer relevant with dirsync obsoleted (as of Messaging Server 6.0).
local.imta.sims_migrate No longer relevant with dirsync obsoleted (as of Messaging Server 6.0).
local.imta.ssrenabled No longer relevant with dirsync obsoleted (as of Messaging Server 6.0).
local.imta.statssamplesize No longer relevant with dirsync obsoleted (as of Messaging Server 6.0).
local.imta.ugfilter No longer relevant with dirsync obsoleted (as of Messaging Server 6.0).
local.imta.vanityenabled Use the DOMAIN_MATCH_URL MTA option instead.
local.installeddir No longer used as of Messaging Server 7.0.
local.instancedir No longer used as of Messaging Server 7.0.
local.lastconfigfetch No longer used as of Messaging Server 7.0.
local.ldapbasedn No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
local.ldapcachefile No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
local.ldapconfigdn No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
local.ldaphost No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
local.ldapisiedn No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
local.ldapport No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
local.ldapsiecred No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
local.ldapsiedn No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
local.ldapuselocal No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
local.ldapusessl No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
local.report.counterlogfile.expirytime Removed in Messaging Server 6.2. No replacement.
local.report.counterlogfile.interval Removed in Messaging Server 6.2. No replacement.
local.report.counterlogfile.level Removed in Messaging Server 6.2. No replacement.
local.report.counterlogfile.logdir Removed in Messaging Server 6.2. No replacement.
local.report.counterlogfile.loglevel Removed in Messaging Server 6.2. No replacement.
local.report.counterlogfile.maxlogfiles Removed in Messaging Server 6.2. No replacement.
local.report.counterlogfile.maxlogfilesize Removed in Messaging Server 6.2. No replacement.
local.report.counterlogfile.maxlogsize Removed in Messaging Server 6.2. No replacement.
local.report.counterlogfile.minfreediskspace Removed in Messaging Server 6.2. No replacement.
local.report.counterlogfile.rollovertime Removed in Messaging Server 6.2. No replacement.
local.report.counterlogfile.separator Removed in Messaging Server 6.2. No replacement.
local.report.job.desc.sample Removed in Messaging Server 6.2. No replacement.
local.report.job.range.sample Removed in Messaging Server 6.2. No replacement.
local.report.job.schedule.sample Removed in Messaging Server 6.2. No replacement.
local.report.job.target.sample Removed in Messaging Server 6.2. No replacement.
local.report.job.type.sample Removed in Messaging Server 6.2. No replacement.
local.report.reportercmd Removed in Messaging Server 6.2. No replacement.
local.report.runinterval Removed in Messaging Server 6.2. No replacement.
local.report.type.cmd.listmbox Removed in Messaging Server 6.2. No replacement.
local.report.type.desc.listmbox Removed in Messaging Server 6.2. No replacement.
local.rfc822header.fixcharset No longer relevant in Messaging Server 6.x and later versions.
local.rfc822header.fixlang No longer relevant in Messaging Server 6.x and later versions.
local.servername Use local.hostname instead (as of Messaging Server 7.0).
local.serverroot No longer used (as of Messaging Server 7.0).
local.servertype Never used (removed as of Messaging Server 7.0).
local.service.http.forceasciifrom No longer necessary.
local.service.http.proxy MEM is obsoleted now that webmail communicates with the store via IMAP (as of Messaging Server 6.3).
local.sharedfoldersforcedsubscription No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
local.store.expire.workday Use local.schedule.expire instead.
local.store.maxlogs Use local.store.maxlog instead.
local.store.notifyplugin.deletemsg.jenable Use local.store.notifyplugin.*.deletemsg.enable instead.
local.store.notifyplugin.jdebuglevel Use local.store.notifyplugin.*.debuglevel instead.
local.store.notifyplugin.jmaxbodysize Use local.store.notifyplugin.*.maxbodysize instead.
local.store.notifyplugin.jmaxheadersize Use local.store.notifyplugin.*.maxheadersize instead.
local.store.notifyplugin.jmqhost Use local.store.notifyplugin.*.jmqhost instead.
local.store.notifyplugin.jmqport Use local.store.notifyplugin.*.jmqport instead.
local.store.notifyplugin.jmqpwd Use local.store.notifyplugin.*.jmqpwd instead.
local.store.notifyplugin.jmqtopic Use local.store.notifyplugin.*.jmqtopic instead.
local.store.notifyplugin.jmquser Use local.store.notifyplugin.*.jmquser instead.
local.store.notifyplugin.loguser.jenable Use local.store.notifyplugin.*.loguser.enable instead.
local.store.notifyplugin.newmsg.jenable Use local.store.notifyplugin.*.newmsg.enable instead.
local.store.notifyplugin.noneinbox.jenable Use local.store.notifyplugin.*.noneinbox.enable instead.
local.store.notifyplugin.purgemsg.jenable Use local.store.notifyplugin.*.purgemsg.enable instead.
local.store.notifyplugin.readmsg.jenable Use local.store.notifyplugin.*.readmsg.enable instead.
local.store.notifyplugin.updatemsg.jenable Use local.store.notifyplugin.*.updatemsg.enable instead.
local.store.serversidewastebasket Never used.
local.ugldapdeforgdn Never used.
local.ugldaphasplainpasswords Use sasl.default.ldap.has_plain_passwords instead.
local.ugldapuselocal No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
local.webmail.sieve.host Unused. Web browser security requires that the sieve reside on the same host as the web page server.
local.webmail.smime.cert.enable Use local.webmail.cert.enable instead.
local.webmail.smime.cert.port Use local.webmail.cert.port instead.
local.webmail.uwcrppsupport Use local.service.http.ims5compat if necessary.
logfile.http.logname Calendar Server parameter. Not used in Messaging Server.
logfiles.admin.alias No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
logfiles.default.alias No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
logfiles.http.alias No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
logfiles.imap.alias No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
logfiles.imta.alias No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
logfiles.pop.alias No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
logfiles.snmp.alias No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
nsclassname No longer relevant with Administration Server obsoleted (as of Messaging Server 6.3).
sasl.default.transition_criteria Use sasl.default.auto_transition instead.
service.http.allowadminproxy Use the LDAP attribute mailAllowedServiceAccess instead.
service.http.proxydomainallowed Use the LDAP attribute mailAllowedServiceAccess instead.
service.ldapmemcache Removed in Messaging Server 5.2p2. Use service.experimentalldapmemcache instead.
service.plaintextloginpause Removed in Messaging Server 5.0. No replacement.
service.pop.popminpoll Removed in SIMS 4.0. No replacement.
service.sslcertbasedn Removed when Administration Server obsoleted (as of Messaging Server 6.3). Use msgcert to manage certificate database instead.
service.sslcertfile Use local.ssldbpath and local.ssldbprefix instead.
service.sslkeyfile Use local.ssldbpath and local.ssldbprefix instead.
service.sslpasswdfile Use local.ssldbpath and local.ssldbprefix instead.
service.sslrequestcert Use msgcert request-cert instead.
store.defaultacl Removed in Messaging Server 6.3.
store.diskflushinterval Use local.store.*synclevel instead.
store.expirestart Use local.schedule.expire instead.

Requirements for Messaging Server 7.0

See Requirements for Communications Suite 6.

Note

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

Messaging Server Installation Notes

These installation notes pertain to the Messaging Server 7.0 release. This section contains the following subsections:

Installation Overview for Messaging Server

Use the Communications Services installer to install Messaging Server.

For installation instructions, see the Communications Suite 6 Installation Guide.

Next, you must configure Messaging Server by:

  • Running the Directory Server Preparation Tool, comm_dssetup.pl .
  • Running the Messaging Server configuration program.

For configuration instructions, see the Communications Suite 6 Initial Configuration information.

comm_dssetup.pl Changes for this Release

The following changes were implemented in the latest version of comm_dssetup.pl, the program that prepares Directory Server for Messaging Server use:

  1. Silent Installation: password change
    -w dirmanager_passwd has been deprecated in favor of -jpasswd_file
  2. See Messaging Server Compatibility Issues for more changes to the comm_dssetup.pl program.

Upgrade Instructions for Messaging Server

If you are upgrading to Messaging Server 7.0 from an earlier release, follow the upgrade instructions in the Communications Suite 6 Upgrade Guide.

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 your host's IP address in the /etc/hosts file, for example:

129.158.230.64 budgie.siroe.varrius.com budgie

Note

On Solaris OS 10 U3 and earlier 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. From Solaris OS 10U4 onwards, the contents of the /etc/inet/ipnodes and /etc/hosts files have been merged together into just the /etc/hosts file. Applying kernel patch 120011-14 on any Solaris 10 system will also perform the merge, and subsequent removal of the /etc/inet/ipnodes file.

Increasing ulimit For Files After Upgrade

Due to bug 6767802 (Store daemons fail to start under cluster control due to file descriptor limits enforced by cluster), fixed in Messaging Server 7.0P3, after upgrading to Messaging Server 7.0, you must increase the number of file descriptors by setting the ulimit as follows:

ulimit -n number_of_file_descriptors

For example:

ulimit -n 100000

For more information about the upgrade procedure, see the Communications Suite 6 Upgrade Guide. For more information on Solaris tunable parameters, see Solaris Tunable Parameters Reference Manual.

This is fixed in Messaging Server 7.0P3

Messaging Server Compatibility Issues

To purge users with iPlanet Delegated Administrator when you are running Messaging Server 6.3, see Purging Users with iPlanet Delegated Administrator and Messaging Server 6.3.

The following table describes compatibility issues with Messaging Server:

Incompatibility Workaround Comments
comm_dssetup.pl, the program that prepares the directory server for Messaging Server (Calendar Server and Delegated Administrator) has been modified to work with both Directory Server 6.0 and Directory Server 5.x: Interactive Mode: Server-root and Directory Server Instances Directory Server instance(s) reside in the server-root, or an explicit Directory Server instance directory Previous versions of Directory Server used the notion of a server-root where multiple instances and configuration info would be housed. Directory Server 6 no longer uses a server-root. Instances may be anywhere. In this question, a user needs to: 1) specify the instance directory. Or, if the user is using previous versions of Directory Server, the user can: 2) specify the server-root directory where the instances are housed. You will be prompted with an additional question to pick an instance from the server-root. Or, 3) a user who has used Directory Server 5x and is now using Directory Server 6 might manually put all of her Directory Server instances under a parent directory (what we used to call a server-root).
Note

Server-root terminology has been removed from Directory Server 6.

 no additional comments
comm_dssetup.pl, the program that prepares the directory server for Messaging Server (Calendar Server and Delegated Administrator) has been modified to work with both Directory Server 6.0 and Directory Server 5.x: Silent Installation: server-root directory In previous versions of Silent installation, you would specify both a server-root and an instance directory. If you are using Directory Server 5.x, this still holds true. Since there is no server-root directory in Directory Server 6.0, you will need to specify the parent directory of the Directory Server instance. no additional comments
The location of the Directory Preparation Tool (comm_dssetup.pl) has changed. comm_dssetup.pl is now in its own package installed in /opt/SUNcomds for Solaris, and /opt/sun/comms/dssetup for Linux
Existing scripts that specify the old path need to be updated. 		To install the package, be sure the Directory Preparation Tool is selected in the appropriate installer panel.
In Messaging Server 5.x, an administrator could use the IMAP listcommand 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.3 Administration Guide.
The configuration program for the Delegated Administrator has changed. Install Delegated Administrator and run the configuration program. The current program is located at:
for Solaris, /opt/SUNWcomm/bin/config-commda
for Linux /opt/sun/comms/config-commda 		Upgrade to the new Delegated Administrator when installing this version of Messaging Server.
Upgrading Messaging Server with Webmail over IMAP protocol change (6397425, 6397451, 2137362) The back-end server must be upgraded before upgrading the front-end server. Both the Webmail over IMAP protocol as well as the back-end message stores must be the same product version. See the Sun Java Communications Suite 5 Upgrade Guide for details. no additional comments
This release of Communications Express is incompatible with the previous version of Messaging 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 6, Sun Java System Communications Express 6.3 Release Notes.
Clarification is needed on RTF/HTML editing and browser compatibility for Messenger Express and Communications Express.
(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 2004Q2 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 2005Q1 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.
"session.timeout Login Again" pop-up error displays when you click Communications Express in Portal Server. (6417988) Ignore the pop-up error, close the window, and continue to use Communications Express. No additional comments.
If you use Messaging Server with Access Manager Single Sign-on, it does not support Java Enterprise System 2004Q2 Access Manager Server. However, Access Manager 6.3 and later is supported. The specific versions of Messaging Server that do not support Java Enterprise System 2004Q2 Access Manager Server are:
  • Messaging Server 6.2-6.01 and later
  • Messaging Server 6.3
 Upgrade Access Manager (JES 2004Q2) before upgrading 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.

Messaging Server Documentation Updates

Messaging Server Compatibility Issues

Problems Fixed in This Release of Messaging Server

6676443

Messaging Server configure utility reports an installation task failure if SNMP is not installed

4991650

Messaging Server does not support a staged rolling upgrade with minimum downtime in a symmetric HA environment

Known Issues and Limitations in Messaging Server

This section describes known issues in the Messaging Server product.

6686339

When imap.numprocesses is set to 10, IMAP flag updates are not working in an IDLE session
When service.imap.numprocesses is set to 1 (default), FLAG updates in an IDLE session can be seen. But if service.imap.numprocesses is set to 10, then flag updates are not seen.

Workaround: Change the MaxNumProducers setting to -1 when using JMQ with IMAP.

6648157

Messaging Server upgrade from 6.3 to 7.0 has one diff3 error in the imta_tailor.new file.
This problem is present in the beta, but is resolved in the beta refresh. If a pre-existing 6.3 or below installation is upgraded to 7.0, patch-config will report a diff3 error in the imta_tailor.new file. The workaround is to manually merge these changes. Open imta_tailor.new in an editor, delete the line beginning with "<<<<<<<" and every line up to and including "=======" except the "IMTA_WORLD_GROUP" line, then leave in any remaining lines which remain except the "IMTA_WORLD_GROUP" line. Finally, and delete the line starting with ">>>>>>>".

For example, if this is the file you begin with:

! $Revision: 1.33 $
!
IMTA_USER=mailsrv
IMTA_USER_USERNAME=nobody
<<<<<<< /opt/sun/comms/messaging/install/migrate/from-6.3-0.15/save/config/imta_tailor.new
IMTA_WORLD_GROUP=mail
IMTA_ROOT=/opt/sun/comms/messaging
[...]
IMTA_HOLD=/opt/sun/comms/messaging/config/hold_list
=======
IMTA_WORLD_GROUP=<local.servergid>
>>>>>>> /opt/sun/comms/messaging/install/migrate/from-6.3-0.15/backout/lib/config-templates/imta_tailor.new.sed

You should edit it manually to become:

! $Revision: 1.33 $
!
IMTA_USER=mailsrv
IMTA_USER_USERNAME=nobody
IMTA_WORLD_GROUP=mail

6569452

The following mailbox database error message can be displayed: "Environment reference count went negative."
The message store processes do not call the underlying database method that generates this error. The error message is thus irrelevant.

Workaround: Ignore the error message.

6654364

The IMAP server closes down a client's connection after the fetch command.
The client's connection to the server should remain open.

No Issue ID

After an upgrade, when you restart the server, the Berkeley Database issues a log version error, issuing the following message: 'Skipping log file...historic log version.'
This is expected behavior. Ignore this message. The Berkeley Database creates a new log file and continues logging into the new file. For example, it creates log.0000000002 and continues.

Redistributable Files for Messaging Server

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

  • You can redistribute the following files in source (HTML and Javascript) or binary form (GIF files) within a licensed Messaging Server distribution only:
    • msg-svr-base/config/html (and subdirectories)
    • msg-svr-base/install/config/html (and subdirectories)
      You are not permitted to distribute these files by themselves.
  • You can copy and use (but not modify) the following header files solely to create and distribute programs to interface with Messaging Server APIs, to compile customer written code using the documented API to interoperate or integrate with Messaging Server, and only as expressly provided in the Messaging Server documentation:
    • msg-svr-base/examples/meauthsdk/expapi.h
    • msg-svr-base/examples/tpauthsdk/authserv.h
    • All files in the msg-svr-base/include directory (default location)
  • The following files are provided solely as reference for writing programs that use the documented API to integrate with Messaging Server:
    • msg-svr-base/examples/meauthsdk/
    • msg-svr-base/examples/tpauthsdk/
    • msg-svr-base/examples/mtasdk/

Labels

releasenotes releasenotes Delete
guide guide Delete
messagingserver messagingserver Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (12)

 

  1. Dec 03, 2007

    katbert says:

    I think this needs to be rephased: First we write: The Messenger Express web...

    I think this needs to be rephased:

    First we write:

    • The Messenger Express webmail interface has been removed from this release

    Then we write

    • Note
    • This deprecation also includes the deprecation of the Messenger Express Mail Filter
      User Interface (msg-svr-base /SUNWmsgmf/MailFilter.war ).

    We state in the paragraph above we've "removed" messenger express, not deprecated.
    Maybe this should read "The Messenger Express mail filters were also removed as part of the Messenger Express removal as they were deprecated as part of the original ME deprecation."

    1. Dec 03, 2007

      JenniferMyers says:

      I agree and changed it as suggested.

      I agree and changed it as suggested.

  2. Dec 03, 2007

    mckeon says:

    The note about having to edit /etc/inet/ipndoes as well as /etc/hosts on Solaris...

    The note about having to edit /etc/inet/ipndoes as well as /etc/hosts
    on Solaris 10, isn't quite correct. It applies to systems running
    Solaris 10U3 or earlier, BUT from Solaris 10U4 onwards the contents of
    /etc/inet/ipnodes and /etc/hosts have been merged together, into just
    /etc/hosts. Applying kernel patch 120011-14 on any Solaris 10 system
    will also perform the merge, and subsequent removal of /etc/inet/ipnodes.

    1. Dec 04, 2007

      joesciallo says:

      Made suggested change.

      Made suggested change.

  3. Dec 04, 2007

    JenniferMyers says:

    Bug fixed. Newly assigned ports are 8990 (http) and 8991 (https).

    Bug fixed. Newly assigned ports are 8990 (http) and 8991 (https).

  4. Mar 13, 2008

    DerekDiget says:

    In the section talking about increasing the number of file descriptors (ulimit)....

    In the section talking about increasing the number of file descriptors (ulimit)..... That was true in Solaris 8 and before. Solaris 9 and 10 have the default ALREADY set to 65536.

    See Solaris Tunable Parameters Reference Manual

    1. Mar 14, 2008

      joesciallo says:

      Derek, Right, AFAIK this has been something we have been documenting for Messag...

      Derek,

      Right, AFAIK this has been something we have been documenting for Messaging Server for some time, at least two releases. It is carry over information from previous release notes, but still applicable.

      I'll add the link you provided to this doc.

      Thanks,

      Joe

  5. Jun 15, 2008

    shjorth_sun says:

    "Red Hat Linux 3 platform support has been deprecated in this release and be rem...

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

    Shouldn't that be, "Communications Suite 6 continues to be supported on Red Hat Linux 4."

    Regards,

    Shane.

    1. Jun 16, 2008

      joesciallo says:

      Shane, I believe you're right. Fixed.

      Shane,

      I believe you're right. Fixed.

  6. Sep 22, 2008

    gigibigi says:

    Hmmm, based on Ignored imta_tailor settings also IMTA_LOG option is obsoleted ...

    Hmmm, based on

    Ignored imta_tailor settings

    also IMTA_LOG option is obsoleted so apparently the IMTA log file location cannot change.

    Is it an undocumented temporary limitation ? Any workaround to suggest ?

    1. Sep 22, 2008

      The_Tech_Writer says:

      This is a documented permanent feature. The entire log directory can be moved t...

      This is a documented permanent feature. The entire log directory can be moved through the use of links. Splitting
      things so logs go into multiple directories is no longer possible. This was a deliberate change. (Note that it won't work to try to symlink-move just particular files, e.g., mail.log_current, since the MTA recreates them.)

      You can find some more discussion of this in the thread on the ims-support and messaging lists dating from mid-August 2008 with

      Subject: Re: Messaging 6.2 to 7.0 Upgrade.

  7. Nov 06, 2008

    mckeon says:

    The section titled "Event Notification Service (ENS)" talks about IMAP IDLE only...

    The section titled "Event Notification Service (ENS)" talks about
    IMAP IDLE only working over ENS. This is totally incorrect. IMAP
    IDLE works with JMQ, and in fact is significantly easier to setup.
    JMQ simply need to be enabled (same instructions as that used for
    JMQ notifications) followed by the command below and a restart of
    the IMAP daemon.

    configutil -o service.imap.idle -v yes

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact