These release notes contain important information about iPlanetTM Messaging Server 5.2. Features and enhancements, installation notes, known problems, and other late-breaking issues are addressed here. Read this document before you install iPlanet Messaging Server.
An electronic version of these release notes can be found at the iPlanet documentation web site: http://docs.iplanet.com/docs/manuals/messaging.html. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and manuals.
These release notes contain the following sections:
iPlanet Messaging Server provides a powerful and flexible solution to the email needs of enterprises and messaging hosts of all sizes using open Internet standards.
iPlanet Messaging Server is an integration of the Netscape Messaging Server and Sun Internet Messaging Server. The most robust and highest performing components of each product have been combined to produce the iPlanet Messaging Server. For example, the message store, LDAP directory, and Administration Console come from Netscape Messaging Server, while the message transfer agent (MTA) and delegated administrator command line interface come from Sun Internet Mail Server.
Because this is an integrated product, Netscape Messaging Server and Sun Internet Messaging Server customers might find that many processes and procedures for those products are different for iPlanet Messaging Server. For complete information refer to the iPlanet Messaging Server 5.2 documentation at http://docs.iplanet.com/docs/manuals/messaging.html.
The following list describes new features specific to Messaging Server 5.2:
The following list describes features carried forward into Messaging Server 5.2:
The following features will be deprecated in this release and will be removed in future releases:
Although Netscape Directory Server 4.x is still supported, you can configure iPlanet Directory Server 5.x support as of this release. Support for Netscape Directory Server 4.x will be dropped in the next release of Messaging Server. Note that the currently planned end of service life for Netscape Directory Server 4.16 is scheduled for January 24, 2003.
See the iPlanet Messaging Server Installation Guide for more information on installing Messaging Server and Directory Server.
The new MTA direct LDAP lookup feature will replace the imsimta dirsync command in the next major release. For more information on using the direct LDAP lookup feature, see the iPlanet Messaging Server Administrator's Guide.
If you currently use Sun Cluster 2.2, it is recommended that you use Sun Cluster 3.x. Support for Sun Cluster 2.2 will be removed in the next release of Messaging Server. For more information on Sun Cluster 3.x, see the iPlanet Messaging Server Installation Guide.
Veritas Cluster Server 1.x support is deprecated and will not be supported in the next release of Messaging Server.
The ability to install multiple instances of Messaging Server in the same server-root directory is now deprecated. While you can still perform this function, it is not recommended that you continue doing so. Instead, multiple Messaging Server instances can be installed on the same disk and host, but they should be installed in separate server-root directories. In the next Messaging Server release, the ability to install multiple instances in the same server-root directory will be removed.
The minimum hardware requirements for iPlanet Messaging Server are:
For Messenger Express access, Messaging Server requires a JavaScript-enabled browser. For optimal performance, iPlanet recommends the following browsers listed in Table 1:
Browsers
Solaris 2.6 and Solaris 8
HP-UX 11.00
Windows NT, Windows 98, Windows 2000
It is strongly recommended that you do not use Netscape Communicator 6.0 with iPlanet Delegated Administrator for Messaging and Collaboration 1.2.
iPlanet Messaging Server is supported on the following platforms:
| Note | Solaris 7 is not a supported platform for iPlanet Messaging Server. However, it has been reported that the Solaris patch 106980-10 for Solaris 7 allows the MTA to properly function.
|
The supported Solaris platforms require the following patches.
A list of recommended patches for Solaris 2.6 and Solaris 8 can be found at http://access1.sun.com.
Additionally, ensure that your Solaris setup specifies how to route to hosts that are not on the local subnet. To do this, ensure that:
The HP-UX 11.0 platform requires the following operating system bundles and patches:
Note that switching the globalmutex back to native implementation can improve performance. To do so, use one of the following HP patches:
If you are running iPlanet Web Server on an HP-UX platform, you need to ensure that the following patches are installed on that machine. (See Product Hierarchy and Dependencies for more information on iPlanet Web Server.) Table 2 lists the required patches for the HP-UX 11.0 (800 series), and Table 3 lists the required patches for the HP-UX 11.0 (700 series):
To identify any existing patches on your system, use the swlist command. To install HP-UX patches, use the swinstall command. Refer to the HP documentation for more information.
A list of recommended patches for HP-UX 11.00 can be found at the following URL: http://us-support.external.hp.com/index.html
Windows NT 4.0 SP6a (Service Pack 6a) is supported.
This section describes platform-specific tuning requirements that are necessary to run iPlanet Messaging Server 5.2, iPlanet Web Server, or iPlanet Delegated Administrator for Messaging and Collaboration.
Certain kernel parameters should be modified to optimize performance for the iPlanet Web Server. The following HP-UX series are described:
Use the HP sam (System Administration Manager) tool to modify and tune specific system parameters. For information on using sam tool, refer to the following link: http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90701/B2355-90701_top.html&con=/hpux/onlinedocs/B2355-90701/00/00/25-con.html&toc=/hpux/onlinedocs/B2355-90701/00/00/25-toc.html&searchterms=sam&queryid=20020130-134720
Parameter
Value
Parameter
Value
iPlanet Messaging Server 5.2 requires the following:
| Note |
|
For iPlanet Web Server, it is strongly recommended that you review the iPlanet Web Server 6.0 SP2 release notes to determine any required operating system patches: http://docs.iplanet.com/docs/manuals/enterprise.html
You cannot upgrade the iPlanet Delegated Administrator from older versions of the product. Instead, you need to uninstall the previous version of iPlanet Delegated Administrator and install the version that are bundled with the new Messaging Server version that you are installing.
These products are all included on the Messaging Server CD at the download site at http://www.iplanet.com/downloads/download/.
This section describes the major bugs that were fixed in the Messaging Server 5.2 release:
Bug Number
Description
Status
Modifications were made to Messenger Express for integration with the iPlanet Portal Server.
In certain scenarios, the imsimta dirsync process was unresponsive.
On Pentium PC and Pentium Xeon machines, the SMTP service would not start on a Windows NT platform. You would receive the following error message: System error 1067.
In Messenger Express, images for emoticons do not show up when the message is read in another client browser.
For details on enabling emoticons, see the section on updates to:
HTML attachments received in a different character set than that being used by the browser displayed incorrectly.
In the Personal Address Book, you could not clear the contents of a field.
Messenger Express did not acknowledge the configutil store.quotawarn parameter.
Using Messenger Express, the vacation message after the ":" got truncated.
Changes to the preferred language setting did not take effect immediately.
Messenger Express did not allow you to edit a recipient name once it was entered; you had to delete and retype the entire entry.
In Messenger Express, you were unable to login if your userID contained single quotes.
In iPlanet Delegated Administrator for Messaging and Collaboration, domain customization using the domain.map file did not work.
ReplayFormat and ProxyAuth configuration options were ignored if the mailAllowedServiceAccess attribute was set on a user entry.
Setting a mailing list to `hidden' did not prevent it from being viewed in the Personal Address Book.
MMP's implementation of PLAIN SASL (RFC 2595) did not correctly support proxy authentication. This implementation is useful for unified messaging systems.
The imadmin user modify command could not change the userpassword attribute.
When a partial line was read, a CPU-consuming loop occurred in POP, IMAP, and MMP servers.
If the same IP address makes frequent connections over a short period of time, MMP would not function properly.
On a Windows NT platform, messages destined for a nonexistent host were not immediately rejected, but instead remained in the send queue for several days before being rejected.
Could not create an aging policy by using the configutil command.
The command-line interface configuration was not read when a custom configuration suffix was used to install iPlanet Delegated Administrator for Messaging and Collaboration.
If the suffix did not already exist in the Directory Server, iPlanet Delegated Administrator for Messaging and Collaboration did not create a configuration suffix.
In Messenger Express, if an attachment's file name contained %20, the %20 was converted to a blank space. On Internet Explorer browsers only.
On Windows NT platforms, some qmadmin commands did not properly function.
The SMTP client and server were enhanced to work around a problem that could cause SMTP connections to be aborted when receiving large messages.
The upgrade option in the Messaging Server installer changed the Messenger Express port.
When the long LdapURL was used, gibberish characters would appear in the log file.
The Messaging Server installer failed to create a unique "Messaging End UserAdministrator" if there was more than one installation against a single Directory server.
See Installation and Uninstallation for additional information on this bug.
Using the -f option on the sendmail line did not cause any response.
The mailDeliveryFileURL parameter to archive a mailing list message did not function.
If you install a second messaging server instance using the same directory server, users who are trying to authenticate to the first messaging installation server were denied access.
If you added an external moderator to a mailing list, the moderator file would be empty.
Delivery Notification messages were not delivered to domain Postmaster.
If the sender's return address was too long, the imsimta run autoreply command would crash.
After migrating to iPlanet Messaging Server from Netscape Messaging Server 4.15, the Personal Address Book users and group names were changed to numbers.
MMP stopped responding when SSL/TLS was used under high load.
in iPlanet Delegated Administrator for Messaging and Collaboration, the domain's allowed service access was not being properly displayed.
Any imadmin command that used the -i option (for bulk loading) did not work.
The Sun Cluster 2.2 High Availability agent did not require tcpclnt.
Using the inetDomainSearchFilter: uid=%U@%V caused problems with Messaging Server services.
Messenger Express was unable to check for uniqueness when creating new folders in Japanese and Chinese versions.
Messenger Express stopped authenticating connections when pointed to iPlanet Directory Access Router server.
Messages from an unauthorized address to certain mailing lists caused a loop in a TCP_SMTP server.
In iPlanet Delegated Administrator for Messaging and Collaboration, the mail filter names were not localizable.
If the DC tree is nested, the Messaging Server processes consumed 100% of the CPU during user login.
The Delegated Administrator searched the incorrect DC suffix.
If you inadvertently configure the imta.cnf file to use a job pool not described in the job_controller.cnf file, a message is now logged in the Job Controller log file indicating a problem.
A truncated store.idx file caused problems with the popd service.
In Planet Delegated Administrator for Messaging and Collaboration, dashes and parentheses could not be entered into any phone field.
MMP used the wrong schema attribute for access control filters. If you were using the old mailAccessDomain attribute in your deployment, you can keep the older behavior by explicitly setting default:TCPAccessAttr to mailAccessDomain. See also bug 4552976.
MMP used the wrong daemon name in access control filters. The MMP used the service names: popmmp, spopmmp, imapmmp and simapmmp for POP, SSL+POP, IMAP and SSL+IMAP respectively. The correct names as documented in the iPlanet Schema Reference Guide are pop, pops, imap, and imaps.
The MoveUser utility failed with replica hosts. Needed the ability to specify a destination server in a replication environment so that after the moveuser command updated the LDAP entry, the destination server was aware of the update. Otherwise, the moveuser command would fail with "Mailbox does not exist" errors.
In order to run the imsdirmig and imsdaaci commands on Windows NT, you had to copy the DLL files libyasr.dll and nsldap32v40.dll from server-root\bin\msg\lib to the directory where these commands are located: server-root\bin\msg\migrate\bin.
When running the imsdirmig migration tool, the -l option did not work.
The imsdirmig migration tool failed to process the Netscape Messaging Server Postmaster entry.
The Delegated Administrator command-line interface gave a error when enabled with SSL.
On HP-UX 11.0, additional configuration steps were needed in order to turn on SSL from imadmin to iPlanet Web Server.
On Windows NT, the Job Controller and Dispatcher never created log files even when configured to do so. They have been changed so that they now honor the debug parameters in job_controller.cnf and dispatcher.cnf files.
The imadmin purge command did not remove the user's Personal Address Book entries.
When an external user sent a message to a subaddress by using the following address format: user+subfolder@domain.com, the +subfolder was stripped. Consequently, mail destined for a shared folder (based on fileinto or shared folder rules) was incorrectly delivered to the INBOX instead. For example, the subaddress of benny+forum@sesta.com was filed in Benny's INBOX instead of the forum subfolder.
The autoreply Option file's RESEND_TIMEOUT option did not work.
Users in domain organization within a hosted domain were unable to login.
If SSL was used by a client when connecting to the MMP and the SSLBacksidePort option was not set, the MMP would still use SSL when connecting to a back-end server.
iPlanet Delegated Administrator for Messaging and Collaboration install broke the merged schema support.
Fixed. See 4547375.
Users without a localized user interface could not create or edit vacation messages in their language when using the default language user interface.
If an authorized sender was an external member of a mailing list, he could not send messages to that list.
On Solaris platforms, the Job Controller sometimes unexpectedly exited if a big backlog existed.
(For UNIX only) The MMP had a hardcoded limit of 32768 file descriptors which would prevent more than 16384 open authenticated proxy connections. The MMP will now use the OS provided hard limit on file descriptors if it is greater than 32768.
The Administration Console .jar files did not get updated during an Messaging Server upgrades.
The Messaging Server upgrade process overwrote the job_controller.cnf and dispatcher.cnf files. For more information on the upgrade process, see the iPlanet Messaging Server Installation Guide.
If you installed two separate installations of Messaging Server that use a common Users and Groups Directory Server, Installer failed to add the msg-admin-xxx account to Messaging End User Administrator group.
If a Service Administrators group already existed, adding a second Messaging Server failed to add its own service administrator into the group.
The default provided by ims_dssetup script, o=internet, had to be accepted by the user. For more information on the ims_dssetup.pl script, see the iPlanet Messaging Server Installation Guide.
If you used a replicated user and group directory server, Messaging Server installation failed.
If you used the store.expirerule.name.foldername.
If a file was manually deleted from a message delivery queue there was a possibility that the delivery process would repeatedly attempt to deliver the (now deleted) message. These attempts would be 10 seconds apart.
folderpattern attribute, you could unintentionally delete messages.
The following sections describe known problems, limitations, and considerations of iPlanet Messaging Server and its components. This section contains the following sub-sections:
The following are known problems, issues, and considerations with the Messaging Server installation and uninstallation.
Except for the Directory Server, the servers are not started by the installer as of iPlanet Messaging Server 5.1.
Note
If you want to install only MMP, follow the steps listed below to select MMP; otherwise the installation will fail:
On UNIX platforms, the directory should be owned by the iPlanet Messaging Server user and group, and have permissions 750.
If you are using Sun Cluster 2.2 or Veritas Cluster Server 1.1, you must uninstall Messaging Server manually.
Be aware that the following procedure will uninstall all components including the message store.
While the Installer program does not require you install the Administration Server component on the Windows NT version, it is mandatory for successful Messaging Server installation.
You must install Messaging Server in an empty directory or a directory that does not already exist. This directory cannot contain any subdirectories that serve as mount points. After you complete the Messaging Server installation, you can create mount points as desired.
Moreover, after uninstalling iPlanet Messaging Server, if you use the same server-root directory that was previously uninstalled, you might get an error during re-installation. You will need to use a new server-root directory when performing the re-installation.
During the uninstallation process, the sendmail program is not restored because it is renamed as sendmail.bk during the original installation process. To restore sendmail, after running the installation program, rename sendmail.bk to sendmail.
When installing Messaging Server, you should write down the administration port number you specify to the installer. You will need to know this port number to use the Administration Console. During an express installation, you are not prompted for an administration port number; instead, the installer chooses a random port number. When you start Console, you will be asked for the administration port number chosen during installation. If you do not know the port number, it is recorded in the following file: server-root/admin-serv/config/adm.conf.
For example, the following installation path would not work:
C:\Program Files\iPlanet\Server5
In this example, there is a space between Program Files, therefore there will be installation problems if this server-root directory path is used.
The Messaging End User Administrators Group has been moved to the organization tree root. During an upgrade from any previous version of Messaging Server to Messaging Server 5.2, the old group will remain with the default domain. However, all related ACIs will properly reference the new group in the organization tree root during the upgrade. While it will not affect any operation, it is highly recommended you manually remove the old group to avoid confusion.
If you install Messaging Server and Directory Server together, and if you specify a suffix that has spaces in it, you must make the following modifications under the DN after installation:
Due to limitations in the iPlanet Messaging Server Sun Cluster 2.2 agent, Messaging Server must be installed at a predetermined mount point, as determined by the $LOGICAL_HOSTNAME environment variable.
If you use the Console interface to manage your servers, you will have a console to manage iPlanet Directory Server 5.x and a console to manage iPlanet Messaging Server 5.2. To manage iPlanet Directory Server 5.x, run startconsole from the directory server server-root to invoke iPlanet 5.0 Console. To manage iPlanet Messaging Server 5.2, run the startconsole command from the messaging server server-root. Running this command will invoke Netscape 4.2 Console. Note which console corresponds to which server. You should only manage iPlanet Messaging Server 5.2 through Netscape Console 4.2, and you should only manage iPlanet Directory Server 5.x through iPlanet Console 5.0.
Occasionally, upon successful installation, error messages might be found in the installation log.
On UNIX, a successful installation ends with the following message: "Go to server-root and enter start console to begin managing your servers." In this message, server-root is the absolute directory path where you chose to install the messaging server, for example: /usr/iplanet/server5.
On Windows NT, a successful installation ends with a prompt asking if the user wants to view the README file or reboot the system.
Currently, the Veritas Cluster framework does not have an HA agent for the Directory server; therefore, the Directory Server will not run as an HA service.
When installing Messaging Server on a computer, do not specify a default domain that is the same as the computer's fully qualified domain name.
The mailbox list database temporary directory (defined by the store.dbtmpdir configutil parameter) is heavily accessed. At installation time, the value of this parameter is not defined and defaults to a subdirectory in the server-root. If the disks that house the mboxlist database temporary directory are not fast enough at very large sites, performance problems might occur.
As part of your performance and tuning steps, you should define a value for this parameter.
This section describes known problems, limitations, and considerations when migrating from earlier versions of Messaging Server.
After adding iPlanet Delegated Administrator for Messaging and Collaboration support, the old Sun Internet Mail Server still appears in certain situations through the iPlanet Delegated Administrator user interface. For example, on the Domain Mail Properties page, creating a user and enabling the mail service for that user will list the old Sun Internet Mail Server mail host. This behavior occurs because migrating from the Sun Internet Mail Server domain preserves the preferredMailHost domain attribute. To fix the problem, change this attribute value to point to the correct mail server.
If a user's uid attribute in LDAP contains any upper case characters (for example, the uppercase K in Kolander) after a migration has occurred from SIMS to iPlanet Messaging Server, the user will not be able to access the migrated mailbox.
SIMS stores all mailbox names in lowercase characters, but iPlanet Messaging Server does not. Moreover, SIMS converts LDAP uid attributes to lowercase characters before it searches its message store for a mailbox name that matches that uid; again, iPlanet Messaging Server does not. During a migration, SIMS mailboxes are restored to iPlanet Messaging Server. In this situation, because the mailboxes were migrated from SIMS, they are all in lowercase characters. Since iPlanet Messaging Server does not convert LDAP uid attributes to lowercase, uid attributes that contain uppercase characters will not match the names of the migrated mailboxes. Mail users with uid attributes containing uppercase characters will not be able to access their mailboxes.
To fix this problem, administrators have two options.
where filename is the name of a file that contains an entry such as the following:
Notice, when using the rename option, DO NOT change the case of the domain portion of the user ID, for example sesta.com. It must remain in lowercase or the mailbox name will not be recognized when a user logs in.
Refer to the iPlanet Messaging Server Reference Manual for more information on renaming users with imsrestore.
When migrating directory entries from Netscape Messaging Server 4.x, specify an LDAP filter— using the -F argument to imsdirmig— that excludes the existing Netscape Messaging Server's postmaster entry. An example of such a filter is -F "(!(cn=postmaster))". This filter will exclude the postmaster entry from the migration processing. If such a filter is not specified, imsdirmig fails to process the entry and exits on the resulting error, unless -c is specified to force imsdirmig to continue processing after it encounters an error.
For information about running the ims_dssetup utility, see the iPlanet Messaging Server Migration Guide, Chapter 3, section titled "Migrating from a Single-Server Netscape Messaging Server System," sub-section titled "Migration Procedures," step 3.
For information about regenerating the index for the above attributes, refer to the iPlanet Directory Server documentation at: http://docs.iplanet.com/docs/manuals/directory/41/admin/
index1.htm#1008974
This section describes known problems, limitations, and considerations when upgrading iPlanet Messaging Server.
The upgrade process now backs up the files in the server-root/msg-instance/html directory and saves them in the server-root/msg-instance/backup.timestamp where timestamp indicates the time at which the installation took place.
The user is prompted by three separate screens, one prompt per screen. The three items that the user is prompted for are: the host name of the iPlanet Delegated Administrator for Messaging and Collaboration (a fully qualified host name), the Web Server port, and the default domain. Though the prompted information is not needed by the server, the simplest work-around is to provide the requested information as demonstrated by the following example:
Host Name of the server: ims.india.sesta.com
Port number of the server: 80
Default Domain: india.sesta.com
If you want to upgrade to iPlanet Messaging Server 5.2 and you have installed Sun Cluster 3.0, Sun Cluster 3.0 Update 1, or Sun Cluster 3.0 Update 2 with a previous version of iPlanet Messaging Server, you should first upgrade the Messaging Server installation. See the Upgrade appendix in the iPlanet Messaging Server Installation Guide.
After completing the Messaging Server installation, you need to install the SUNWscims package (from the Messaging Server 5.2 CDROM) on each cluster node. For more information, see the HA installation chapter (specifically the section on Sun Cluster 3.0 U1 and U2 Agent Installation) in the iPlanet Messaging Server Installation Guide. This process will upgrade your Messaging Server HA Agent.
If you are upgrading from a previous version of iPlanet Messaging Server, you will have to make changes to two existing ACIs in the user and group LDAP directory server.
The Organization Tree base suffix and the Domain Component Tree base suffix have an ACI that grants the end user administrator account write-access to certain user attributes. Attribute mailMessageStore must be added to the existing ACI.
The ACIs are on the root nodes of the Organization and Domain Component trees. The ACIs to be modified have the name Messaging Server End User Adminstrator Write Access Rights - product=ims5.0,class=installer,num=101,version=1.
The best way to modify the ACIs in question is by using the Directory Server Console.
Prior to upgrading to Messaging Server 5.2, stop the Messaging Server processes (by using stop-msg.bat) and manually delete the *.share files in the server-root\msg-instance\imta\tmp directory. You can also delete the *.share files after the upgrade, however, to avoid hung processes at that point, you might need to reboot your system prior to deleting the files.
Since the configuration files from the previous version of Messaging Server are backed up and used during the upgrade process, the "factory default" settings of the Messaging Server 5.2 MTA configuration files are not incorporated in the upgrade. Consequently, the configuration files will not pick up any new changes after the upgrade process.
The following procedures outline two methods for incorporating any customizations from your previous version of the MTA configuration files and the new settings in the Messaging Server 5.2 configuration files:
Method 1: To Add New Settings to the Previous Version of the MTA Configuration Files.
For example:
ims-ms defragment subdirs 20 notices 1 7 14 21 28 backoff "pt5m"
"pt10m" "pt30m" "pt1h" "pt2h" "pt4h" maxjobs 1 pool IMS_POOL
fileinto $U+$S@$D filter ssrd:$A
For UNIX platforms:
root@default_domain: postmaster
root@localhost: postmaster
postmaster@localhost: postmaster
For Windows NT platforms:
postmaster@localhost: postmaster
Replace default_domain with your default mail domain and localhost with the host name where Messaging Server is installed.
Method 2: To Add Your Customized Settings from the Previous Version of the MTA Configuration Files to the Messaging Server 5.2 Version of the Configuration Files.
This command also indicates the cmdpath (the path to the JRE command and should be prepended to the jre -cp command) and the runpath (directory in which to run the command).
If the server-root/msg-instance/iplanet-msg-install.log file has the following entry:
Then, the following example describes how to execute the jre -cp command:
The JRE command will append its output to the imtaconfig.log file.
|
# cd server-root/msg-instance
# ./imsimta cnbuild # ./imsimta refresh |
This command also indicates the cmdpath (the path to the JRE command and should be prepended to the jre -cp command) and the runpath (directory in which to run the command).
If the c:\temp\iplanet-msg-install.log file has the following entry:
Then, the following example describes how to execute the jre -cp command:
The JRE command will append its output to the imtaconfig.log file.
|
cd server-root\msg-instance
imsimta cnbuild imsimta refresh |
By default, the ENS service is set for manual startup in Messaging Server 5.1. However, in Messaging Server 5.2, the ENS service performs an automatic startup on reboot. After upgrading to Messaging Server 5.2, the setting does not change from manual to automatic.
Work-around: The following steps will change the default setting of the ENS Service from manual to automatic startup.
This section describes known problems, limitations, and considerations with iPlanet Messaging Server.
This constraint is enforced by iPlanet Delegated Administrator for Messaging and Collaboration as well as the MTA when operating in direct LDAP mode. Allowing these characters in the User ID can cause problems in the message store. If you want to change the list of characters forbidden by the MTA, set the following option by listing a comma-separated string of the characters' ASCII values:
LDAP_UID_INVALID_CHARS="32,33,34,35,36,37,38,40,41,42,43,44,47,58,59,60,61,
62,63,64,91,92,93,96,123,125,126"
in the server-root/msg-instance/imta/config/options.dat file. Note that you are strongly advised against relaxing this constraint.
The SMTP server's default behavior permissively accepts various line terminators. Currently, the smtp keyword is synonymous to the smtp_crorlf channel keyword on the tcp channels. While this behavior complies with the original SMTP specification (RFC 821), it does not comply with the latest revision of the SMTP specification (RFC 2821).
In the next major release of Messaging Server (after the Messaging Server 5.2 release), the meaning of the smtp keyword and the default behavior of the tcp channels will comply with the revised standard. Specifically, the smtp keyword will become synonymous to the smtp_crlf channel keyword. For more information, see the section on "Channel Protocol Selection and Line Terminators" in the chapter on Configuring Channel Definitions in the iPlanet Messaging Server Administrator's Guide.
NFS is not supported for several reasons, including: open with O_EXCL is non-atomic. This technique is used for synchronizing deferred handling between various threads.
To customize or localize notifications, you would create a complete set of return_*.txt files for each locale and/or customization and store it in a separate directory. For example, you could have French notification files stored in one directory, Spanish for another, and notifications for a special unsolicited bulk email channel stored in a third. Sample files for French, German, and Spanish are included in this release. These files can be modified to suit your specific needs. Refer to Chapter 6 of the iPlanet Messaging Server Administrator's Guide for complete information on Customizing and Localizing Notification Messages.
To do so, use the following configutil command:
local.service.http.proxy.port.hostname
For example, if the host name is webmail.sesta.com and the port number is 8888, the command would be in the following format:
configutil -o local.service.http.proxy.port.webmail.sesta.com -v 8888
This is a known Solaris bug. To avoid this problem, be sure to run the nscd service. For more information on nscd, refer to the Solaris man page.
If you use the imsimta dirsync option, the total length of all forwarding addresses is limited to 1024 characters. If the total length of all forwarding addresses exceeds 1024 characters, it is recommended that you use the mailing lists feature. Note that if you use the MTA direct LDAP feature, you will not encounter this limitation.
The Messaging Server installation fails if it is installed in the ko locale as a result of this problem.
Work-around: Install the Directory Server in a separate server-root directory from Messaging Server. Then, manually run ims_dssetup.pl on the Directory Server, using the default C locale instead of the ko locale.
Alternatively, you can install Messaging Server using another Korean locale, such as ko_KR.EUC, ko.UTF-8, or ko_KR.UTF-8.
This affects many searches performed by iPlanet Messaging Server, and is especially apparent when using the dirsync utility. To speed up searches use directory manager credentials to access the directory by using the following commands:
msg-instance/configutil -o local.ugldapbinddn -v "rootdn" -l
msg-instance/configutil -o local.ugldapbindcred -v "rootdn_passwd" -l
where rootdn and rootdn_passwd are the credentials of the Directory Server's administrator.
Note that you can now utilize the Direct LDAP Lookup feature which obviates the need to use the imsimta dirsync command. For more information, refer to the iPlanet Messaging Server Administrator's Guide.
Refer to the chapter on logging and log analysis in the iPlanet Messaging Server Administrator's Guide on how to enable SMTP logging.
For information on installation and configuring Sun Cluster 3.0 Update 1 or later, refer to the iPlanet Messaging Server Installation Guide.
While trying to add dynamic criteria to groups for email-only membership through the Messaging Console, the test button to test the dynamic criterion (also known as the LDAP URL) does not work. The functionality of email membership of the group will not be broken by this limitation.
The stored only recognizes INADDR_ANY, a constant value known internally to the server that specifies that this listen socket is listening to all IP addresses for this machine.
To work around this problem, you can deploy separate MMP servers to handle the clients that are excluded from bad guy rules. These servers must have BadGuy turned off.
When working with mapping entries that use libimtamap.so, for example:
* $C$[IMTA_LIBMAP,immap_is_in_list_of_ip,$2|IMTA_TABLE:/ip.txt|$$Y]$E, do not use strings that require variable substitution from the imta_tailor file. Instead, you should write out the full directory path as shown in the following example:
* $C$[IMTA_LIBMAP,immap_is_in_list_of_ip,$2|/iplanet/server5/msg-siroe/imta/
config/ip.txt|$$Y]$E
When the user tree hierarchy contains nodes other than "ou", "o", "dc", or "c", the parallel PAB hierarchy must be created manually. For example, if you have users under dept=1234,o=acme.com you need to create dept=1234,o=acme.com,o=pab.
When you create a user or group through the Administration Console, ensure that you are selecting the correct organizational unit (ou) under which you want to create a user or group. To do so, use the drop-down list to choose New Organizational Unit; then click Create.
In the Select Organizational Unit window, select the directory subtree (ou) to which the organizational unit will belong. Placing your cursor on any of the directory subtrees will reveal the complete DN of the organizational unit.
If Help does not launch from the Administration Console, create a script called "netscape", such as the one given below, and place this script in your path:
On Windows NT, the Administration Console Help does not come up if a browser is already open. If it is not open it brings up a browser and the pages can be viewed. To work around this behavior move server-root\bin\base\viewurl.exe somewhere else, or rename the file, for example rename the file to viewulr.exe.hide.
When creating a new user in the Administration Console 4.2 in a localized environment, you may not be able to enter 8-bit characters (for example, Ë) in the First Name, Last Name, and Common Name fields.
Work-around: Enter the 8-bit character into a non-Console application, copy the character, and then paste it into the Administration Console, using <Control> + V, or use iPlanet Delegated Administrator for Messaging and Collaboration.
When moving mailboxes to different partitions, a user should be disconnected from the messaging server before the using the mboxutil -r option; once the mailbox is moved, the user should be reconnected to the server.
The instructions to turn on CRAM-MD5/DIGEST-MD5 do not work for "external" SMTP connections (by default all connections not from the local host). However, it works as documented for IMAP/POP and internal SMTP connections. To fix this problem, run:
configutil -o sasl.external.ldap.has_plain_passwords -v 1
The auto-reply subject line in Messaging Server Console does not provide multi-language support. If the attribute mailautoreplysubject;lang-XX (where XX is the language) is already set in Messenger Express or in iPlanet Delegated Administrator for Messaging and Collaboration, the mailautoreplysubject attribute cannot be viewed or changed through the Messaging Console, since the Console looks for the attribute mailautoreplysubject, not mailautoreplysubject;lang-XX.
When configuring "Host Names to allow" for the Administration Server, the access control list is case-sensitive. If the DNS server uses mixed-case host names in the IN-ADDR records (used when translating from an IP address to a domain name), the access control list must use the same case. For example, if your host is test.Sesta.Com, then the access control list must include *.Sesta.Com. Due to this bug, *.sesta.com will not suffice.
For example, if the user/group base suffix is o=isp, then the DN of the service administrator group is cn=Service Administrators,ou=groups,o=isp. To designate the account uid=ofanning, o=sesta.com, o=isp as a service administrator, you should add the account's DN to the group. In the following modify record, the designated user is added as a group member in the LDIF:
dn: cn=Service Administrators,ou=groups,o=isp
changetype: modify
add: uniquemember
uniquemember: uid=ofanning, o=sesta.com, o=isp
Furthermore, for users to have service administrator privileges, the attribute memberof must be added to the user entry and set to the Service Administrator Group, for example:
For example, the following command returns an error if the expiration rule name does not already exist: configutil -o store.expirerule.name.folderpattern -v pattern
Use Console instead of the command line. After an expiration rule is created, you can modify the parameters by using the configutil utility.
Due to the caching scheme, changing domain properties such as authorized services or status in LDAP does not take effect in IMAP, POP, SMTP, and HTTP until these services are restarted.
The sslpassword.conf file is not created when an SSL certificate is created from the console. This occurs when only the console, administration server, and MMP are installed (no Messaging Server or Directory Server).
mgrpErrorsTo attribute does not support multiple values. If you want to specify multiple recipients for error messages, create a mailing list and specify the mailing list address as the value for the mgrpErrorsTo attribute.
To enable the workaround, set the following configuration variable:
configutil -o local.imap.immediateflagupdate -v yes
If, while using the work-around, you experience performance issues, it is recommended that you discontinue using the work-around.
In the quotacheck utility, the -d option for specifying the domain does not work for the default domain. Furthermore, the quotacheck utility returns incorrect error messages when the -u and -n options are specified.
The Netscape browser might not display some Japanese Kanji characters properly in certain unicode font sizes (10, for example). To fix this, change the browser's unicode font size to 14.
If you wish to use the program delivery feature, the user under which iPlanet Messaging Server runs must have a home directory, and must have permission to create and write files in the home directory.
For example, you might see an error message such as:
Cluster.PMF.pmfd: Error opening procfs control file
/proc/384/ctl for tag rg.rs.0.svc: No such file or directory
You can ignore these messages.
If an incremental dirsync is in progress at the time of an HA failover, the alias database will be marked as unsafe. The administrator will be notified of this condition when the messaging server is brought back online. The following message will appear in the log/imta/dirsync.trx-XXXX file:
When this occurs, run the following: imsimta recover-crash
Any updates that occurred since the imsimta dirsync -F command was last run will be lost. After running imsimta recover-crash, run: imsimta dirsync -F
Note that you do not encounter this problem if you use the MTA Direct LDAP function.
The IMAP, POP, and HTTP servers cache the LDAP entries of users who have recently logged in for the amount of time specified in the service.authcachettl configuration parameter. To make the deletion of a user immediately effective, you can run the servers with no authentication cache or turn off the authentication cache by setting service.authcachettl to 0 using the configutil utility and restarting all the services. Note, a setting of 0 will have an impact on performance.
This problem also applies to the Messaging Multiplexor (MMP); however, the MMP does not use configutil. It has a separate AuthCachTTL option in its configuration file.
If there is a short form version of a domain name in the /etc/hosts file, there will be problems if you use a host name in an access control filter. When the IP address lookup returns a short form version of the domain name, the match will fail. Therefore, you should make sure you use a fully qualified domain name in the /etc/hosts file.
Work-around: After running the ha_ip_config script, run the following configutil command:
server-root/msg-instance/configutil -o service.http.smtphost -v logical_IP
For more information on running the ha_ip_config script, see the High Availability chapter in the iPlanet Messaging Server Installation Guide for UNIX.
On Windows NT, the imsimta cleandb command does not remove the *.share files in the server-root\msg-instance\imta\tmp directory.
Work-around: Manually remove all the *.share files in the server-root\msg-instance\imta\tmp directory, specifically the __db_lock.share and __db_mpool.share files. Note these files can only be removed when the MTA processes are not using them. Therefore, you should first stop the MTA processes by using the imsimta shutdown command before removing the *.share files.
The rewrite rule in the following comment in the imta.cnf file is incorrect:
! Uncomment the next line for Direct LDAP mode
! $* $E$F$U%$H@budgie.siroe.com$V$H
Instead, the rewrite rule should state the following:
! Uncomment the next line for Direct LDAP mode
! $* $E$F$U%$H$V$H@budgie.siroe.com
This is a known Sun Cluster 3.0 U2 (Update 2) problem that is due to a condition between the monitoring thread and an incoming stop. See Sun Cluster bugs: 4498808 and 4368936.
Work-around: Add -y Retry_count = 1 to the following command (Step 11 in "Configuring Messaging Server HA Support for Sun Cluster" in the iPlanet Messaging Server Installation Guide for UNIX):
# scrgadm -a -j ha-ldap -t SUNW.nsldap -g IMS-RG \
-x Confdir_list=/global/ims/server5/slapd-mail \
-y Retry_count=1
-y Resource_dependencies=ha-storage
If you install iPlanet Directory Server 5.1 and Messaging Server on the same machine, you will see two Server Groups in the Administration Console — one for Directory Server (Server Group) and one for Messaging Server (Server Group (2)). If you click Server Group (the server group for Directory Server), the Console becomes unresponsive, and you will see error messages in a terminal window. Similarly, in iPlanet Console 5.0, if you click the server group for Messaging Server (Server Group (2)), you will see an error message in a terminal window and any running operation will fail; however, the console does not become unresponsive.
Work-around: For Netscape Console, in the msgserver-root/java/jars directory, replace the following files:
ds51.jar, ds51_en.jar, admserv51.jar, and admserv51_en.jar with zero-length versions of the files with the same names. If you click Server Group in the Netscape Console, you will see the following error messages and will not be allowed to inadvertantly access the wrong server:
Similarly, for iPlanet Console, in the dirserver-root/java/jars directory, replace the following files:
msgadmin52.jar, msgadmin52.icon, msgadmin52_en.jar, mcc42.jar, mcc42_en.jar, admserv42.jar, admserv42_en.jar, admserv42.icon, nmclf42.jar, and nmclf42_en.jar
with zero-length versions of the files. If you click Server Group (2) in the iPlanet Console, you will see error messages and will not be allowed to inadvertantly access the wrong server.
See also bug: 4560710 in Installation and Uninstallation. For more information on iPlanet Directory Server 5.1 and Messaging Server, see Appendix A of the iPlanet Messaging Server Installation Guide.
The following are known problems with iPlanet Delegated Administrator for Messaging and Collaboration.
Note that the use of the provisioning utility imadmin requires that iPlanet Delegated Administrator for Messaging and Collaboration be installed.
In addition, Single Sign-on for iPlanet Delegated Administrator for Messaging and Collaboration does not function through the standard portal gateway. Contact technical support for upcoming hotfixes.
In the jvm12.conf file in directory webserver-root/https-instance, increase the minHeapSize to 3.5M and maxHeapSize to 64M.
While using Internet Explorer, make sure you set your cache settings to check for a newer version of stored Web pages on every visit to the page. If you set it to `Automatically,' some pages will display cached values that might not be current.
Work-around: Perform an ldapsearch, and be sure to specify the attribute in the attribute list to be returned.
When using iPlanet Delegated Administrator for Messaging and Collaboration, to set the delivery options for a user whose mailhost is a Windows NT server, do not select Native as a delivery option. Selecting Native as the only option for mail delivery for such users will result in the mail message being bounced to the sender. The bounce message will be sent only after several days have elapsed. If you want bounce messages to be sent immediately for mail that is undeliverable because the user erroneously selected this inappropriate delivery method, add the following rewrite rule to msginstance/imta/config/imta.cnf:
native-daemon $?unix/native delivery not supported on server
To remove a user from a family group, Service/Domain/Family group Administrators can use the imadmin family-member remove command, which is available from the command line interface.
Messaging Server provisioning tools (iPlanet Delegated Administrator GUI and imadmin command) fail to create a hosted domain when a subdomain of that domain was previously created as a hosted domain. For example, if sales.sesta.com was created first, later attempts to create sesta.com as a hosted domain would fail.
To define sesta.com as a hosted domain, follow the procedure in the iPlanet Messaging Server Provisioning Guide in order to determine how to overlay the existing entry for sesta.com with the additional object classes. You also need to create an organization container for the domain sesta.com with all the required ACIs (Appendix A, iPlanet Messaging Server Provisioning Guide) and create the domain admin group for the domain.
If your Messaging Server deployment has separate Configuration and User/Group directories, the iPlanet Delegated Administrator configuration cannot be stored in a separate directory from the User/Group directory. Instead, the iPlanet Delegated Administrator configuration must be stored in the User/Group directory.
When logged-in as a Top-Level Administrator, you cannot create or manage a mail list. As a work-around, traverse to any of the hosted domains before clicking on the My Account icon.
iPlanet Delegated Administrator for Messaging and Collaboration allows you to create a new domain and have it point at an existing user/group subtree. This subtree must contain the domain administrator and postmaster groups. However, the creation of a domain when pointed at an existing user/group subtree fails as an invalid check is made for the domain administrator group under the root suffix of the user/group tree.
A workaround is to create these groups under the root suffix. The LDIF for creating these groups is shown below. The following variables are used in the LDIF examples and should be replaced with the appropriate values for the installation.
BASE SUFFIX = root suffix of the user/group tree for the hosted domain (for example: o=sesta.com, o=isp)
DOMAIN NAME = domain name of the domain being added
With iPlanet Delegated Administrator for Messaging and Collaboration, you can create cn and cn:lang-xx attributes; however, the product does not have an interface to modify these attributes. To modify these attributes, use imadmin user modify with the -A option. Note that administrators are allowed to modify the cn but not the cn:lang-xx attribute.
Though Class of Service templates can be assigned when you edit a user, you cannot assign them during user creation in iPlanet Delegated Administrator for Messaging and Collaboration.
If you want to activate the counters for users, mail lists, and domains, you can enable these plug-ins with Netscape Directory Server 4.16. However, if you are using iPlanet Directory Server 5.1, these counter plug-ins are not available. Therefore, you will not be able to restrict the number of users or groups in a domain if you use iPlanet Directory Server 5.1.
If you set up auto-reply messages for users, and you enter multiple auto-reply subject and message texts for multiple languages at the same time, you need to save the changes for each individual language one at a time. If you enter the changes for all languages and attempt to save them at the same time, some of the information in the auto-reply message will be missing or not properly saved.
If you are setting up Class of Service (CoS) for users in an organization, and you edit a user through iPlanet Delegated Administrator for Messaging and Collaboration, you should be able to choose or modify a CoS template for that user. However, this feature does not properly function if you use iPlanet Directory Server 5.x and iPlanet Delegated Administrator for Messaging and Collaboration.
If your changes in iPlanet Delegated Administrator for Messaging and Collaboration are not being saved, and the Save/Apply button does not appear work, make sure that you shift the focus of the cursor from the last changed field by pressing the Tab key. Then, press the Save/Apply button to save the changes.
If you login to iPlanet Delegated Administrator for Messaging and Collaboration and type the Messenger Express URL in the same Web browser window, you are asked to authenticate again into Messenger Express.
Note that you can use single sign-on from Messenger Express to iPlanet Delegated Administrator for Messaging and Collaboration.
The following are known problems with iPlanet Messenger Express:
The spellchecker expects a character with an umlaut ( for example, Ü) to be a character followed by double quote. (for example, u" ). When displaying words with umlauts, the spellchecker instead displays a character followed by a double quote.
Work-around: Use Internet Explorer version 5.5 SP2 (Service Pack 2) on the rare instance that you experience this behavior.
Due to timing issues in Internet Explorer builds before 5.5 SP1, very large messages are truncated on slower machines with small amounts of memory. Use the recommended build of Internet Explorer 5.5 SP2.
Several minor glitches occur related to either javascript dialog or IMAP folder issues; users who run into these issues might want to use another browser.
When using Netscape Communicator 4.x on Solaris in a Japanese EUC locale, the vcard of a message is displayed as gibberish.
A user will not be able to attach files with Japanese file names using Netscape Communicator 4.x browser on Solaris.
Work-around: On the blank screen, click the right mouse button and select "Reload Frame." You do not need to restart the web browser.
This scenario exists when your Messaging Server is on a Solaris 2.6 operating environment or a Windows NT platform and the Messenger Express client is running on an Internet Explorer 5.5 SP2 (Service Pack 2) Web browser on either a Windows 98 or Windows 2000 platform.
Note that the Directory Server is exhibiting correct behavior. Due to a bug in Netscape Directory Server 4.x, you are able to enter multiple email IDs.
When you open the Compose window from the Folders tab, compose a message, and click Send or Save Draft, you will see a Javascript error if you are using Internet Explorer 6.0 as your client web browser. Despite the error, the message is sent (if you click Send) or saved (if you click Save Draft) as expected.
This section describes any errors or changes to the iPlanet Messaging Server 5.2 documentation set.
The online version of the iPlanet Messaging Server Administrator's Guide contains up-to-date changes not found in the CD version: For the online version, see: http://docs.iplanet.com/docs/manuals/messaging.html
Note
This section describes any errors or changes to the iPlanet Delegated Administrator for Messaging and Collaboration Installation and Administration Guide.
The documentation supporting the Calendar Support question (Install Screen 5-Calendar Server) should state the following:
Install Screen 5—Calendar Server
--------------------------------------------------------------------------
Sun-Netscape Alliance
iPlanet Delegated Administrator for Messaging Installation/Uninstallation
--------------------------------------------------------------------------
If you want iPlanet Delegated Administrator for Messaging to manage an iPlanet Calendar Server, enter 'Yes'.
Manage Calendar Server [No]: __________________
-----------------------------------------------------------------------------
Select the default value No, since this feature is currently not available.
When this feature is supported in a future release, selecting Yes will enable iPlanet calendar service support through iPlanet Delegated Administrator for Messaging and Collaboration.
This section describes any errors or changes to the iPlanet Messenger Express Customization Guide.
In order to enable emoticons, the variable iconHREF in the main.js file (located in directory: msgserver-root/html) must be assigned the full path of the location where the emoticon .gif files are located.
For example, if the emoticon files are in the msgserver-name/imx/ directory, then the iconHREF must be set the main.js file to:
var iconHREF = `http://msgserver-name/imx/'
By default, the emoticon .gif files are located in msgserver-root/html/imx and can be copied to another directory. The emoticon files in the /imx/ directory are the following:
angel.gif,angry.gif,grin.gif,devil.gif,smile.gif,laugh.gif,love.gif,sad.gif,
winkwink.gif,sleep.gif.
The configured URL needs to be accessible from the public internet because messages composed using Messenger Express will include references to these URLs in order to represent emoticons.
The Messenger Express client interface can be customized partially or entirely per domain. To do this, create a directory with the domain name under the html directory. Populate this directory with the customized versions of the files from the original directory hierarchy. For example, if you only want to change the icon for the siroe domain, you need to add a new icon in siroe.com's imx directory and change the reference to it in main.js:
html/... // default interface
html/imx/... // default interface
html/en/... // default interface
html/siroe.com/main.js // refers to imx/cat.gif
html/siroe.com/imx/cat.gif
After login, the server refers the user agent to pick up the file: domain/lang/main.html. This is the file that contains references to the rest of the interface. The client requests all the files which make the interface in the directory. If these files exist, they are displayed. Otherwise, there is a fallback to the default setup files. If you have multiple domains but only a few distinct brands, you can use links to make the server use the correct version:
html/... // default interface
html/sesta.com/... // customized interface for brand 1
html/varrius.com -> sesta.com // varrius uses brand 1's interface
The server listens on all IP addresses and can still present a customized interface before login occurs. It does so by looking at the URL and determines if it contains a known domain presenting a per-domain login screen.
For example with the following per-domain login screen, http://webmail.sesta.com/, the server sends the page html/sesta.com/en/default.html
In this case, a user doesn't need to append @domain to his user name in order to log in.
The server needs to be restarted for changes in the contents of the directory server-root/msg-instance/html to take effect.
By default, the folder list displays the following header fields: Date Received, email ID of sender, Subject, and X-priority. To customize these header fields, you can modify the listFrameHTML() and header()functions in the server-root/msg-instance/html/msg_fs.html file.
This code example does not work because the code is not able to take the entry from the i18n_ldap_controls() function in in18n.js. To work around this problem, change the directory server name in the file instanceroot/html/lang_code/lookup_fs.html to the desired directory server name. The name is defined in the function s_SearchCtrl.
The following information should be included in the guide.
The Messenger Express server loads a default set of LDAP attributes for a user at the start of a session. These attributes are as follows:
cn, givenName, mail, mailAlternateAddress, mailAutoReplyMode, mailAutoReplySubject, mailAutoReplyText, mailAutoReplyTextInternal, mailAutoReplyTimeout, mailDeliveryOption, mailForwardingAddress, mailQuota,mailMsgQuota, preferredLanguage, sn, uid, vacationEndDate, vacationStartDate
You might want to obtain other customized LDAP attributes from the server. For example, an ISP might have a custom LDAP attribute assigned to all users called myuserclass. This attribute could denote different types of users that access services, including Messenger Express. Possible values for this attribute are regular and vip. Depending on the type of user (that is, the value of the myuserclass LDAP attribute), different advertisement types will be presented to the user when they log into Messenger Express (Messenger Express is customized to display banner advertisement). If the customized client has access to the myuserclass LDAP attribute, the type of user can be determined and the relevant banner advertisement for that user type can be displayed.
To obtain other customized LDAP attributes from the server, use configutil to modify the service.http.extrauserldapattrs configuration parameter. The attributes are read-only by default. If the customer wants to modify an attribute using the Messenger Express code, that attribute needs to be marked read-write by appending the suffix: w
The example below assumes the customer wants to display banner advertisements depending on the class of the user and that the client program allows the user to edit a link to a home page: configutil -l -o service.http.extrauserldapattrs -v myuserclass,homepage:w
To create your own dictionary for your Messenger Express spell checker, you need to build a binary hash file and copy it to the msgserver-root/dict directory:
The dictionary file contains language-specific vocabulary and the affix file contains grammar rules for the specific language. Refer to the following link that specifies available dictionary and affix files as well as instructions on how to obtain these files: http://fmg-www.cs.ucla.edu/fmg-members/geoff/ispell-dictionaries.html
The French and English (United States) directories are shipped with this version of the Messenger Express and are located in the msgserver-root/dict directory.
|
buildhash dictionary_file affix_file language_name.hash
|
The language_name in the language_name.hash file is the two-letter language code used by Messenger Express (such as: en for English, fr for French). To determine your language's two-letter code, use the msgserver-root/msg-instance/configutil | grep local.supportedlanguages command.
Note
In the following UNIX platform example, an Italian hash file (it.hash) is created by using the buildhash utility. The it.hash file is then copied to the msgserver-root/dict directory. Finally, the mshttpd service is restarted to enable the Messenger Express spell checker:
# cd /usr/iplanet/server5/dict/bin
# ./buildhash italian.dico italian.aff it.hash
# cp it.hash ..
# /usr/iplanet/server5/msg-budgie/start-msg http
This section describes any errors or changes to the iPlanet Messaging Server Migration Guide.
If you have problems with iPlanet Messaging Server, contact iPlanet customer support using one of the following mechanisms:
So that we can best assist you in resolving problems, please have the following information available when you contact support:
Useful iPlanet information can be found at the following Internet locations:
Last Updated May 14, 2002