CHAPTER 3 |
Software Limitations |
This chapter describes known software limitations and updates for the SIMS 4.0 product.
Note - Go to http://sun.com/sims/ for updated release notes and other product information concerning the Sun Internet Mail Server (SIMS) 4.0.
The following steps should be performed after upgrading from Solaris 2.6 to Solaris 7 (and after installing SIMS 4.0):
| 1. | Add the libldap patch for Solaris 7 (107555 for SPARC / 107556 for Intel). |
| 2. | Rename /usr/lib/sendmail to /usr/lib/sendmail.orig:
|
| 3. | Create a symbolic link from /opt/SUNWmail/imta/bin/sendmail to /usr/lib/sendmail:
|
This section addresses the issues when SIMS 4.0 is running. Specifically, these bugs may be found when using the Administration Console, with particular command line utilities, files, or at runtime in general.
When adding users under a hosted domain, the name of the mail host must be provided.
For example, a user (jdoe) needs to be added to the hosted domain stream.com. The mail host for stream.com is bridge.net on host name alpha. When adding jdoe with the imadmin add user command, the following is a portion of what is entered:
The -H option in the above example should be the mail host name (alpha.bridge.net) and not the hosted domain name (alpha.stream.com).
The same should be specified when adding a user via the SIMS Admin Console.
Description: The imadmin [add | delete | modify | purge] user commands incorrectly ignore the -d option and successfully add users to the domain referred to by the -n option.
Workaround: There is no workaround. The command succeeds when it should actually fail.
Description: The imadmin [add | delete | modify | purge] group commands incorrectly ignore the -d option and successfully add groups to the domain referred to by the -n option.
Workaround: There is no workaround. The command succeeds when it should actually fail.
Description: The following configuration variables in the ims.cnf configuration file are not supported in the Admin Console:
|
|
ims-auth-timeout |
|
|
ims-md5auth-enable |
|
|
ims-popb4smpt-timeout |
|
|
ims-popb4smtp-lib |
|
|
ims-client-lookup |
Workaround: Use the imedit utility to edit the ims.cnf configuration file in order to change the parameter values.
Description: The DIT browser in the Admin Console does not display the People,Groups node for a domain that is in the OSI style. The People and Groups cannot be displayed because the Find and Display All buttons require either People or Groups to be selected.
Workaround: Use the Choose Domain to Browse field and enter the newly created domain. When the domain is displayed in the mail directory window, People and Groups are displayed.
Description: When a user entry is concurrently modified (by using both the Admin Console and the CLI tools) the modification is allowed when it should not be allowed.
Workaround: Avoid running the Admin Console and the CLI concurrently on the same data.
Description: The new autoreply channel is visible and configurable through the Admin Console. However, this channel is strictly for future use. Changes made to this channel (via the Admin Console or manual editing) will not have an effect on the autoreply program in this release of SIMS.
Workaround: No workaround exists.
This section describes limitations relating to the directory and directory services.
Description: Adding a long distribution list name (approximately 75 characters or more) can crash the directory server.
Workaround: Do not add distribution lists with names longer than 75 characters.
All text data stored in the directory, such as user names, group descriptions, company names, etc., must be in ASCII. It is not guaranteed that anything besides 7-big ASCII will work.
This section describes limitations relating to the IMTA.
Description: Distribution lists do not support some multi-valued attributes such as moderator and requests-to. It retrieves and recognizes only the first value it fins for these attributes.
Workaround: No workaround exists.
SIMS IMTA log files must be periodically examined and purged or they will continue to grow and fill up your disk. The IMTA log files are located in /var/opt/SUNWmail/imta/log.
Description: If maildeliveryoption is native but the mailmessagestore attribute is not set to /var/mail, mail delivery does not work. Also, if mailmessagestore is set to /var/mail instead of /var/mail/ delivery does not work.
Workaround: If the mailmessagestore attribute is set to /var/mail, change it to /var/mail/. If the mailmessagestore attribute is set to something else, add a new rewrite rule for the pipe channel section in the imta.cnf file:
This section describes limitations relating to the message store.
An iconv bug exists which causes imaccessd to crash when searching for ISO-2022-JP email messages.
All message store utilities will operate on the entire message store by default. Some of the message store utilities have the added option to specify only a specific domain on which to operate. If the SIMS administrator forgets to specify the desired domain on these utilities, they will target or operate on the entire message store.
The options for the imcheck utility have changed between SIMS 3.5 and SIMS 4.0. Please see the man page (imcheck(1M)) for more information. One difference is with the user test option (-u). The user test previously only ran when the message store was down, and would attempt to fix any corrupted folders it found. Now the user test by default runs in a read-only mode This does not fix any folders, but can be run while the message store is up. If the old version of the user test is desired, the SIMS administrator should run imcheck with the -u and -w options. This requires the message store to be down.
This section describes the open issues for the Delegated Management Console.
In previous SIMS releases, the emailuser.html page allowed the user to set alternate delivery program options. This feature does not exist in SIMS 4.0.
Description: An error (Error 404: Not Found) results when you select online help for the Login ID field within the Search area on the Create Distribution List page.
Workaround: No workaround exists. The Edit User page correctly displays the online help for the Login ID field, if the exact help text is desired.
Password information is passed from the user to the directory and back through a series of programs. Both the user and ISP need to know the user's password. The password's transmission path is:
| 1. | Web browser to HTTP server | |
| 2. | HTTP server to CGI program | |
| 3. | CGI program to Delegated Management server | |
| 4. | Delegated Management server to the directory |
A default setup will send this password in plain text along the entire transmission path from the web browser to the directory. This means that the password can be viewed "as is" during transmission. In order to make the password secure, each transmission path needs to be addressed. The following methods can be used to secure the password (and all the other data):
|
|
Use the SSL facility for the transmission between the web browser and the HTTP server. |
|
|
The path between the HTTP server and the CGI program is not at risk because information is posted. |
|
|
The transmission between the CGI program, the Delegated Management server, and the directory may be protected by an IP-based protection method. |
This section describes the open issues/workarounds for the Web Access client.
WebAccess 1.2 depends on the following publicly available standard extensions to Java:
|
|
Java Naming and Directory Interface (JNDI) API version 1.1.1 |
|
|
JavaMail API version 1.1.1 |
These standard extensions are included with the WebAccess 1.2 release.
/etc/init.d/im.server starts the sws_server for the SIMS Admin Console, but not for WebAccess. The WebAccess instance off the Sun Web Server needs to be started manually if WebAccess is installed but the system is not rebooted.
To start WebAccess, execute the following:
Description: Logging into WebAccess with a valid user account using the HotJava browser can appear fail or produce a blank page.
Workaround: Click the Reload button on the web browser or attempt to login again.
Description: Using the HotJava browser, it is possible to access a user account after exiting by clicking the Back button.
Workaround: No workaround exists.
This section describes internationalization/localization issues and limitations.
In the enable.I18N.txt file, the lines under the entry 3 contains errors:
The lines should be changed to:
The lines in Step 3 of the example contains errors:
The lines should be changed to: