Oracle® eMail Server

Release Notes

Release 5.2 for Sun SPARC Solaris 2.6

January 2001

Part No. A86648-01

These release notes accompany Oracle eMail Server Release 5.2 for Sun SPARC Solaris 2.6. They contain the following topics:

• What's New in this Release?

• Client Certification

• Known Limitations

• Known Bugs

• Integration

• Doc Errata

• Additional References

What's New in this Release?

Release 5.2 of Oracle eMail Server ships with both iAS version 1.0.2.1, and the Oracle 8.1.7 database server, and is certified to work in conjunction with Oracle Internet Directory release 2.1.1. New features include:

• ES Thin Client Sample Application -- a browser-based dynamic HTML e-mail client

• Protocol Server Directory Lookup -- provides increased scalability and improved performance of message delivery in multi-node installations

• Monitor charts -- administrators can now monitor capacity and usage of the e-mail system using charts

• Virus Cleanup Tool -- PL/SQL procedure that allows an administrator to define the "fingerprint" of e-mail virus suspects and set them aside for review by an administrator

• Postman Sorting -- faster delivery of messages when queues are long

Client Certification

Oracle eMail Server supports standard IMAP4/POP3 clients. This product has been certified and tested against the following:

• Netscape 4.75

• Outlook Express 5.5

• Lotus Notes R5

• MS Outlook 98

• MS Outlook 2000

Known Limitations

The following are known limitations for Oracle eMail Server:

• If a production system is upgraded from 4.3, 4.2, or any other version prior to 5.0, the system can contain undelivered messages that the new 5.2 server no longer processes. This is because the new version of the server uses a more efficient method of mail delivery that is not compatible with the old algorithm.

  As a solution, configure a postman instance with the NOTIFICATION parameter set to value 1. Run the postman instance for one day to clear up all old undelivered messages. This instance can be deregistered since the NOTIFICATION parameter is no longer used in Oracle eMail Server 5.2.

• Do not use spaces in object names. Use an underscore instead of the space. This does not apply for descriptions or address lines.

  For example, use John_Smith instead of John Smith.

• If the timeout for the IMAP messaging session is shorter than the timeout for the Web Client JSP session, an exception message may appear. Re-login will correct the problem.

Known Bugs

The following bugs are known to exist in Oracle eMail Server Release 5.2.

• 0726152: Multibyte characters cannot be read when a message body is encoded with Base64

• 1338861: The imconfig file fails at the end of the installation when the value of shared_pool_size is specified with a suffix, such as 150M. Error message returned is sql error, check configuration of node, failed internal representation. The sql statement that returns the error is:

  SELECT value
  

  FROM v$parameter
  WHERE UPPER(name) = SHARED_POOL_SIZE
  

  Workaround: Change the init.ora value to be the full integer representation, e.g 150M changes to 150000000.

• 1275791: Cannot create subfolder under a folder if the public subfolder has the same name. For example, it is not possible to have a folder "\public\folder1" and a second folder "\folder1."

• 1420020: If a message has its priority changed to high by the Server Side Rules, the change in priority is not displayed through the Thin Client.

• 1500429: You must ensure that all pending replicator packages have been successfully applied on all nodes before upgrading any node to eMail Server version 5.2. This is necessary to ensure that the data in some of the replicator packages will not override other objects if applied after upgrade has been completed. Also, before you upgrade, make sure that the replicator folders do not have any messages in them, including the wastebasket folder. See the Oracle eMail Server Administration Guide for the correct syntax of the command. For information about how to check the replicator queue, see Chapter 15, "Managing Replication," in the Oracle eMail Server Administration Guide.

• 1567927: Replication of e-mail name service into an LDAP server does not work in multi-domain sites.The RESULTING_MIGRATION_DOMAIN parameter is not correctly read in by individual instances of the IOODSSYNC process (synchronization from eMail Server to the LDAP server).

  Note: ODSIOSYNC uses the RESULTING_MIGRATION_DOMAIN parameter correctly so no special workaround is needed.

  Workaround: Override the global RESULTING_MIGRATION_DOMAIN parameter with an individual eMail Server person object parameter ldapusersuffix. Accounts that use the eMail Server directory as the source to populate an LDAP directory should have the person object parameter set for all individual users before synchronizing.

• 1561765: Users sending messages using Lotus Notes will find that a sent message gets put into the sent folder AND the wastebasket.

The following bugs are known to exist in the Thin Client:

• 1485419: Accounts with greater than 1000 folders cannot be opened.

• 1532186: MSIE rich composer does not work on Macintosh platforms.

• 1403162: Netscape browser will sometimes only print the first visible page of information and not the entire message view

• 1540468: Rules whose name length is greater than 80 characters will cause a problem

• 1482630: The message search criteria uses 1000 bytes as 1K while the search query uses 1024 bytes as 1K for data returned

• 1450070: Folder names with %, ', ", and space cause problems and should not be used

• 1540746: Netscape Messenger client will not display high priority messages as high priority if received from the Thin Client. MS Outlook clients will display high priority correctly.

• 1540700: Display of special characters (ASCII 160-255) in folder names is not supported

• 1517102: If the session times out during message composition, use the back button to return to the message compose screen and copy the text of your message to your clipboard. Re-login, navigate to the compose message tab, and paste the text into the window.

• 1471472: Web Client is not NLS compliant. Folders created with another e-mail client and the folder name containing NLS characters, are not displayed.

• 1574647: When using MSIE: Text disappears if it is sent with a background color

• 1574126: TOTAL_SIZE of the folder to which the virus tool moves an infected message, becomes negative.

Integration

The following information applies if you are integrating eMail Server with Internet Application Server (iAS).

• To integrate with iAS, you must create two $ORACLE_HOME directories. In one $ORACLE_HOME directory, install iAS, Unified Messaging web node, Thin Client, and, if you choose, the protocol servers. Install the database, eMail Server, and Unified Messaging database node in the other $ORACLE_HOME directory.

  Note: Additional iAS integration information may be included in the iAS release documentation.

The following information applies if you are running eMail Server and the e-mail component of Internet File System (iFS) on the same machine.

• The iFS e-mail component and the Oracle eMail Server both use Sendmail for mail transfer. However, iFS requires Sendmail version 8.9.3 or later and eMail Server requires versions of Sendmail later than 8.

• iFS ships an open source version of Sendmail 8.9.3 for Solaris and other UNIX ports. Windows NT and 2000 based installations require you to purchase Sendmail Inc.'s Sendmail version 3.0 or Sendmail version 3.0.2, respectively, for both e-mail components.

• iFS uses a post-installation script to configure the iFS e-mail component. This includes setting up the Sendmail 8.9.3 executable and generating the sendmail.cf file. For more details, please refer to the Post Installation steps in the iFS Installation Guide. To configure the sendmail.cf file for eMail Server, see Chapter 3, "Postinstallation," in the Oracle eMail Server Installation Guide.

• iFS generates a new sendmail.cf file using its automated configuration script (ifsemailsetup). In order to have both the Oracle eMail Server and iFS working on the same machine, it is imperative that the changes required for the Oracle eMail Server be incorporated into the sendmail.cf file generated by the iFS setup scripts. This implies that this can only be done after the iFS configuation script has generated the sendmail.cf file. Please note that the iFS setup script script will overwrite any changes made to the sendmail.cf file after generation.

• If the IMAP servers provided by the Internet File System (iFS) and the eMail Server products are to be run on the same machine, they must be configured to run on different ports on that machine.

  For example, the eMail Server IMAP server can listen on the default port 143 and the iFS IMAP server can be configured to another port appropriate to the installation's requirements. For iFS, this is done by running the iFS configuration utility, and for eMail Server, through the eMail Server Administration tool. The clients accessing the IMAP servers must have accounts mapped to these specific ports. To access both servers at the same time, you must use clients that allow you to set the IMAP port number. Alternatively, you can run the two IMAP4 servers on two different Internet Application Servers.

Doc Errata

The following changes apply to the Oracle eMail Server Installation Guide:

• Chapter 2, "Installing and Configuring Oracle eMail Server"

  The first note under "Task 5: Upgrade an Existing eMail Server Node" of the "Configuring Oracle eMail Server" section, should be disregarded. Instead, there should be an additional step at the end of the task:

  After the setup wizard is finished, copy the config files form
  $ORACLE_HOME/office/admin to $ORACLE_HOME
/office/config/SID.

• Chapter 2, "Installing and Configuring Oracle eMail Server"

  In "Task 5: Upgrade an Existing eMail Server Node" of the "Configuring Oracle eMail Server" section, to upgrade an existing eMail Server installation, the Oracle Universal Installer (OUI) will need to be run as in the "Installing Oracle eMail Server" section of this chapter. The options will be the same. The OUI will detect the previous version, deinstall it, and procede with the upgrade without any intervention.

• Chapter 3, "Postinstallation"

  In Step 1 of "Task 5: Configure SMTP Gateway and Create Aliases," the syntax

  Mofcmail, [tab] P=$ORACLE_HOME/bin/ofcuto, F=rlSsDCFMPpmn, S=10, 
  R=20,[tab]A=ofcuto - $ORACLE_HOME $ORACLE_SID -f config_file - 
  
  $g $a $b $f $x ( $u )
  
  

  should read as follows:

  Mofcmail,[tab]P=$ORACLE_HOME/bin/ofcuto, F=rlSsDCFMPpmn, S=10, 
  R=20,[tab]A=ofcuto - $ORACLE_HOME $ORACLE_SID -f config_file - $g $a 
  $b $f $x ( $u )
  
  

  There should be no spaces around the [tab]'s.

• Chapter 3, "Postinstallation"

  In Step 2 of Step 7 of "Task 5: Configure SMTP Gateway and Create Aliases," the syntax

  Mlocal,[tab]P=$ORACLE_HOME/bin/ofcuto, F=rlSsDCFMPpmn, S=10, 
  R=20,[tab]A=ofcuto-$ORACLE_HOME -f config_file -$g $a $b $f $x ($u
  
  

  should read as follows:

  Mlocal,[tab]P=$ORACLE_HOME/bin/ofcuto, F=rlSsDCFMPpmn, S=10, 
  R=20,[tab]A=ofcuto-$ORACLE_HOME $ORACLE_SID -fconfig_file -$g $a $b 
  $f $x ($u)
  
  

  Insert $ORACLE_SID after the second $ORACLE_HOME. The last character of the line should be ")", as noted above.

• Chapter 3, "Postinstallation"

  In Step 1 of "Task 8: Set Up the ESPrefs Server," the first paragraph should read as follows:

  Copy the espref directory, and all subdirectories from the build environment to $ORACLE_HOME/Apache/Apache/
htdocs/espref.

  Note: "Build environment" in the above paragraph refers to $ORACLE_HOME/office/admin/esprefs.

• Chapter 3, "Postinstallation"

  "Task 9: Configure eMail Server Thin Client" should read as follows:

  Note: The Thin Client must be installed on the $ORACLE_HOME where iAS is installed.

1. Get the esclient.tar and escommonjars.tar from
   $ES_HOME/office/admin, where $ES_HOME is the
   $ORACLE_HOME where eMail Server is intalled. Put both .tar files into $ORACLE_HOME/Apache/Apache/htdocs, where
   $ORACLE_HOME is the directory in which iAS is installed.

   % cd $ORACLE_HOME/Apache/Apache/htdocs
   % tar -xvf esclient.tar
   % mv esclient_oid211 esclient
   % cd esclient/lib
   % tar -xvf ../../escommonjars.tar
   
   

2. To set up iAS to run the Thin Client, perform the following steps:

   Open $ORACLE_HOME/Apache/Jserv/etc/jserv.properties and use text editor to verify that the following lines are contained in the file:

   wrapper.bin.parameters=-DES_PROPERTIES=$ORACLE_HOME/Apache/Apache
   
   /htdocs/esclient/es.properties
   wrapper.classpath=$ORACLE_HOME/Apache/Apache/htdocs/esclient
   
   /lib/j2ee.jar 
   wrapper.classpath=$ORACLE_HOME/Apache/Apache/htdocs/esclient
   
   /lib/jgl.zip 
   wrapper.classpath=$ORACLE_HOME/Apache/Apache/htdocs/esclient
   
   /lib/ldap.jar 
   wrapper.classpath=$ORACLE_HOME/Apache/Apache/htdocs/esclient
   
   /lib/es.jar
   
   

   Use a text editor to verify or insert the following lines into the zone.properties file, also located in the $ORACLE_HOME/Apache
/Jserv/etc directory:

   repositories=$ORACLE_HOME/Apache/Apache/htdocs/esclient/servlets
   
   

3. Configure Oracle Internet Directory (OiD) by loading *.dat files found in $ORACLE_HOME/Apache/Apache/htdocs/esclient/doc, as follows:

   % ldapadd -h host -D 'cn=orcladmin' -w password> -f *.dat
   

   See Also: Oracle Internet Directory Administrator's Guide for more information about loading the preferences schema manually using the OiD administrator's console. The orclMailApplicationPreferences.readme file contains a list of required attributes.

   Load DIT file using the following command:

   % ldapadd -h host -D 'cn=orcladmin' -w password -f oracle.ldif
   
   

4. Configure the es.properties file located in the $ORACLE_HOME/
   Apache/Apache/htdocs/esclient directory using the text editor. Instructions on how to configure this file are located within the es.properties file.

5. Test to see that the Thin Client works. Restart iAS, open a browser, and enter the following url:

   http://hostname:port/esclient/templates/login.jsp
   
   

   You should see the logon page.

The following changes apply to the Oracle eMail Server Administration Guide:

• Chapter 10, "Managing Protocol Server Processes"

  The "Configuring Support for IMAP4 Users to Change Passwords" section is obsolete. To change passwords, see Chapter 3, "ESPrefs Self Service Utility."

• Chapter 7, "Managing the SMTP Gateway in Sendmail"

  In the "Registering the SMTP Gateway with Sendmail" section, change:

  Mofcmail,[tab]P=$ORACLE_HOME/bin/ofcuto, F=rlSsDCFMPpmn, S=10, 
  R=20,[tab]A=ofcuto - $ORACLE_HOME -f config_file - $g $a $b $f $x ( 
  $u )
  
  

  to

  Mofcmail,[tab]P=$ORACLE_HOME/bin/ofcuto, F=rlSsDCFMPpmn, S=10, R=20, 
  [tab]A=ofcuto - $ORACLE_HOME $ORACLE_SID -f config_file - $g $a $b 
  $f $x ( $u )
  
  

  adding $ORACLE_SID to the string after the second $ORACLE_HOME.

Additional References

For information not covered in these Release Notes, see the following:

• Oracle eMail Server Administration Guide Release 5.2

• eMail Server Messaging Developer's Guide Release 5.2

• Oracle eMail Server Installation Guide Release 5.2

• Oracle Support Services web site at:

  http://www.oracle.com/support