Oracle® eMail Server

Release Notes

Release 5.2 for HP 9000 Series HP-UX May 2001

Part No. A90436-01

These release notes accompany Oracle eMail Server Release 5.2 for HP 9000 Series HP-UX. It contains the following topics:

What's New in this Release?

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

ES Thin Client Sample Application

A browser-based dynamic HTML email client.
Protocol Server Directory Lookup

Provides increased scalability and improved performance of message delivery in multi-node installations.
Monitor charts

Enables administrators to monitor capacity and usage of the email system.
Virus Cleanup Tool

PL/SQL procedure that allows an administrator to define the "fingerprint" of email virus suspects and set them aside for review by an administrator.
Postman Sorting
Provides faster delivery of messages when queues are long.

Contents of the CD-ROM

Oracle eMail Server Release 5.2 includes the following:

CD Title	Contents
Oracle eMail Server Release 5.2 for HP 9000 Series HP-UX	Oracle eMail Server for HP 9000 Series HP-UX with 128-bit SSL encryption Administration Tool for HP 9000 Series HP-UX

CD Title

Contents

Oracle eMail Server
Release 5.2
for HP 9000 Series HP-UX

Oracle eMail Server for HP 9000 Series HP-UX with 128-bit SSL encryption

Administration Tool for HP 9000 Series HP-UX

The Oracle eMail Server product shipment also includes a restricted use license for:

Oracle Internet Directory Release 2.1.1
Oracle 8.1.7 Data Server

Installation Overview

Oracle eMail Server is a highly scalable messaging framework that provides complete messaging services. Before the installation, plan your implementation strategy and be familiar with the Oracle eMail Server system components, concepts, and terminology described in Part I of the Oracle Email Server Understanding and Planning Guide.

The installation process is composed of the following steps:

Read Part I of the Oracle Email Server Understanding and Planning Guide to plan your implementation.
Complete the necessary pre-installation tasks including backing up an existing system, configuring the UNIX environment, and preparing related processes and products for the installation.
Use the Installer on the Oracle software CD to install or upgrade Oracle eMail Server and related software products.
Verify the installation by running the root.sh script, starting processes, and checking process logs.

When you have verified the installation, refer to the Oracle eMail Server Administration Guide for instructions on how to configure, maintain, and optimize Oracle eMail Server.

Requirements

To install Oracle eMail Server, you require the following:

An Oracle8i Universal Data Server installed
A CD-ROM drive supported by HP-UX 11.0
The Oracle eMail Server Release 5.2 CD-ROM

Hardware Requirements

For each server identified in your configuration (node, dedicated protocol server, LDAP server, test system), you must determine hardware requirements. These include CPU, disk, and networking requirements.

To make support easier, it is often best to choose a single hardware provider for all your hardware and to have the same or similar hardware configurations.

To install Oracle eMail Server products included with this release, your HP-UX 11.0 system must meet the minimum hardware requirements listed in the following table:

Hardware	Requirements
Memory	A minimum of 256 MB RAM is required to install Oracle eMail Server products.
Swap Space	Twice the amount of RAM or at least 512 MB, whichever is greater, is recommended for most systems.
CD-ROM Device	A CD-ROM drive supported by HP-UX is required. Oracle uses ISO 9660 format CD-ROM disks with RockRidge extensions.

To determine the amount of RAM memory installed on your system, use the HP-UX performance monitor tool glance.

$ glance

To determine the bytes of swap space currently configured on your system, enter the following command:

$ swapinfo -a

CPU Requirements

The metric for CPU usage is the number of SPECint_rate95 points used during steady state activity. SPECint_rate95 is a benchmark designed to measure the possible throughput of integer calculations for a given system and is applicable for this database application.

See Also:

For more information on SPECint_rate95 and a list of systems and their SPECint_rate95 ratings, refer to http://www.spec.org/osg/cpu95/results/rint95.html

The following rates are the SPECint_rate95 demands needed for the different Oracle eMail Server processes for 1000 users at sample light, medium, and heavy workloads.

Process	Light Work Loads	Medium Work Loads	Heavy Work Loads
Oracle8i Universal Data Server	30	50	110
IMAP4	2	4	8
POP3	1	1	2
SMTP/MIME Gateway processes	14	18	40
Postman	2	3	6
Total demands	49	75	168

Memory Requirements

The memory required for the background processes for Oracle8 Universal data Server and the Oracle eMail Server depend on the configuration of the database, features selected for Oracle eMail Server and the number of concurrent users to be supported. The following table illustrates the memory usage for the base install and the incremental memory demands as the workload increases.

Process	Base Memory Demand (MB)	Incremental Memory Demand Per User (MB)
UNIX OS	30 MB	5 MB per 1000 connected IMAP4 clients
X Windows Manager (if launched)	15 MB	0
Oracle8 Universal data Server + static IM background processes	50 MB	0
Database buffer Cache	20 MB	10 MB per 1000 users^{Foot 1}
SGA	10 MB	4.5 MB per 1000 users
Database connections	0	15 MB per 1000 users^{Foot 2}
Postman processes	4 MB	2 MB per 1000 users
IMAP4 process	10 MB	120 MB per 1000 users^{Foot 3}
POP3 process	10 MB	5 MB per 1000 users^{Foot 4}
Sendmail and ofcuto	2 MB	23 MB per 1000 users connected^{Foot 5}
SMTP/MIME Gateway process	10 MB	3.5 MB per 250 users

¹ The database buffer cache can be tuned to hold database blocks and reduce disk I/O and improve response times. Please refer to the documentation provided with the Oracle database for tuning of this memory parameter. The number provided is a generic prescription to handle most messaging workloads.
² The SPS architecture has many different requests being handled by a few static database connections. Given the high volume of traffic over these few connections, the Oracle multi-threaded Server Option should not be used. The number of database connections needed to sustain a user population depends upon the rate of incoming requests and the rate in which the requests are handled. If the incoming rate is very high and the server is handling each request slowly the required number of database connections will go up.
³ This memory requirement is for the number of IMAP4 clients actually holding a socket with the server. Netscape and other IMAP4 clients close their socket with the server if no activity is determined after a preset amount of time. Netscape closes the socket after two uneventful get mail cycles. The user is not aware of being "disconnected" as the client automatically reconnects upon the next user action.
⁴ A thread is launched to handle the incoming POP3 request. The thread is only in existence during the get mail cycle, therefore the total memory consumption at any given time is quite low.
⁵ When a message comes in via SMTP, a new sendmail process is launched to handle the message. Sendmail writes the message to the sendmail queue directory and then either sends the message to outside the intranet or hands it off for local delivery. If there is a bottleneck in the system such as insufficient disk I/O capacity the number of resident processes can grow. If there is insufficient physical memory to handle the necessary processes, the resulting paging disk I/O will slow down the system and increase the number of resident processes.

Disk Space Requirements

Consider the following factors when determining the disk requirements for Oracle eMail Server:

Disk space required by the operating system and other applications
Swap space required by the operating system
Space required for archiving, backup and disk mirroring
Space for Oracle software, such as Oracle8i Universal Data Server, SQL*Plus, and Oracle eMail Server
Space for the Oracle database objects
Number of separate disk drives to handle IO requests

See your operating system, application and system maintenance documentation for information on the first three factors.

Space for Oracle Software

Oracle eMail Server with Oracle 8.1.7	750 MB
Oracle SPS tier	255 MB
Oracle eMail Administration	44 MB

Space for the Oracle Database Objects

The following tablespaces are required for an Oracle eMail Server system. Sizing information is based on a configuration where Oracle eMail Server is the only application.

System Tablespaces

SYSTEM	40 MB minimum
TOOLS	default
USERS	default
RBS (rollback)	20 MB minimum
TEMP	5 MB + (100Kb * number of users)

Oracle eMail Server Tablespaces

OFC_MAIN	10 MB (minimum)
OFC_INDS	(size of OFC_MAIN) * 0.4
OFC_MESG	5 MB + (quota * number of users)
OFC_INDB	(size of OFC_MESG) * 0.1
OFC_CTX	10 MB (minimum)

Number of Separate Disk Drives to Handle IO Requests

The number of disk IO operations/second that a device can handle is highly dependent on the types of disks, number of controllers, if RAID is used or any other striping strategy and the mix of IO requests on the device. In general, a modern single SCSI II drive can handle 40 disk IO operations/second.

The following estimates show the number of disk IO operations per second will be needed. Add disks to the hardware configuration to reduce the disk IO operations per second on each disk.

Process	Light users	Medium users	Heavy user
Oracle database and associated processes	45	130	180
SMTP/MIME Gateway	5	9	18
Sendmail	18	34	64
Total IOs per second	68	173	262

Networking Bandwidth Requirements

The following estimates show average bandwidth requirements for 100 users. These numbers should be added to the values for the existing network usage.

The middle tier is composed of the IMAP4, POP3, and Sendmail processes.

User profile	Bandwidth on Middle Tier	Bandwidth on Database Tier
Heavy	2.9 Mbps	1.8 Mbps
Medium	.7 Mbps	.45 Mbps
Light	.18 Mbps	.12 Mbps

Software Requirements

The following sections list the software requirements.

Operating System Software Requirements

To install Oracle eMail Server products included with this release, your HP-UX system must meet the operating system requirements listed in the following table.

OS Software	Requirements
Operating System	HP-UX 11.0 with stream pipes enabled.
Operating System Patches	See the Oracle8i Release Notes for HP 9000 Series HP-UX to find further information.
Window Manager	X-windows must be installed on the system from where the Installer is run. Use any HP-UX supported X-windows server. Character mode installs are not supported for Release 5.2.
Required Executables	The following executables must be present in the `/usr/ccs/bin` directory: `make`, `ar`, `ld`, `nm`.

To determine your current operating system information, enter the following command:

$ uname -a

To determine which operating system patches are installed, enter the following command:

$ swinstall -p

To determine which operating system packages are installed, enter the following command:

$ swlist -i [package_name]

If you enter swlist -i, all installed packages are listed.

To determine if your X-windows system is working properly on your local system, enter the following command:

$ xclock

If a clock is not displayed on your screen, X-windows is not configured correctly.

To determine if you are using the correct system executables, enter the following commands:

$ /usr/bin/which make
$ /usr/bin/which ar
$ /usr/bin/which ld
$ /usr/bin/which nm
$ /usr/bin/which cc

Each of the five commands above should point to the /usr/ccs/bin directory. If not, add /usr/ccs/bin to the beginning of the PATH environment variable in the current shell.

Enabling Streampipes in HP-UX

You need to generate the kernel to enable STREAMS-based pipes in HP-UX. This step is required for the protocol servers to work.

To generate a kernel that supports STREAMS-based pipes:

STREAMS/UX must be installed.
The module pipemod and the driver pipedev must be included in the /stand/system file. pipemod and pipedev are automatically added to the system file when STREAMS/UX is installed.
The streampipes tunable parameter must be set to 1 in the /stand/system file. This is not automatically set when STREAMS/UX is installed.
The kernel must be generated and the system rebooted.

See Also:
For more information, see STREAMS/UX in the HP 9000 Reference Manual or UNIX man pages on pipe.

Component Software Requirements

Oracle eMail Server requires the following software components and associated releases:

Software Requirements	Release	State During Oracle eMail Server Installation
Oracle eMail Server	5.2
Network Listener	8.1.7	Running
Net8	8.1.7	Installed
Oracle database server	8.1.7	Installed and Running
PL/SQL	8.1.7	Installed
SQL*Plus	8.1.7	Installed
JRE	1.1.8	Installed
JSP engine (iAS)	3.0	Installed and Running
JSDK	2.0 and higher	Installed
Oracle JDBC	8.0.4 and higher	Installed

Pre-Installation Tasks

Perform the following preinstallation tasks described in this section to prepare for Oracle eMail Server installations and upgrades.

Configuring the UNIX Environment

Set the UNIX environment variables required to install and run Oracle eMail Server components. Add these settings to a .cshrc (C shell) or .profile (Bourne or Korn shell) for the Oracle eMail Server database owner.

Let ulimit (Bourne or Korn shell) or limit (C shell) to unlimited or to the maximum value to allow the root.sh postinstallation script to complete without errors. Run the command appropriate for your shell environment to set the maximum file size that can be created on your system.

For more information on ulimit and limit, refer to the UNIX man pages.
Ensure that the DISPLAY environment variable is set to your display address.

In C shell, set DISPLAY as follows:
```
% setenv DISPLAY <hostname>:0.0
```
In Bourne or Korn shell, set DISPLAY as follows:
```
$ DISPLAY=<hostname>:0.0;export DISPLAY
```
Ensure that xhost, while physically located on the host system, is set to enable access to the X server on your system. Use the following command:
```
$ /usr/bin/x11/xhost +
access control disabled, clients can connect from any host
```
See the UNIX man pages for more information on xhost.

Ensure that the following environment variables are set.

Environment Variable	Setting
SHLIB_PATH	Place `$ORACLE_HOME/lib` before any other path entries. It must also contain `/usr/lib.`
ORACLE_HOME	The Oracle8i Universal Data Server home directory.
ORACLE_SID	The Oracle8i Universal Data Server ID.
ORACLE_BASE	Set ORACLE_BASE to point to the JRE location.
PATH	Include `$ORACLE_HOME/bin`, `/bin`, `/usr/local/bin` (or any valid local bin directory to which the database owner can write), `/usr/bin`, and `/usr/ccs/bin`. Also include the `make` utility directory.
SRCHOME	Unset.
TMPDIR	Unset.
TWO_TASK	Unset.
TZ	Set to the timezone offset for your region. This step is required in addition to the GMT offset specified during installation.

Mounting the Product CD-ROM

The Oracle eMail Server CD-ROM is in ISO 9660 format with Rockridge extensions.

You must have root privileges to mount or unmount the CD-ROM manually. Be sure to unmount the CD-ROM before removing it from the drive by using the umount command.

Use a system editor to add the following line to the /etc/pfs_fstab file.

Syntax

<device_file> <mount_point> <filesystem_type> <translation_method>

The first entry is the CD-ROM device file; the second is the mount point. The third indicates that the CD-ROM to be mounted is in IS0 9660 format with RockRidge extensions.

Example

 /dev/dsk/c5t2d0 /SD_CDROM pfs-rrip xlat=unix 1 0

Enter the following command.

$ nohup /usr/sbin/pfs_mountd &

Enter the following command.

$ nohup /usr/sbin/pfsd &

Place the CD-ROM into the tray and run the following command to mount the CD-ROM:

$ /usr/sbin/pfs_mount /SD_CDROM

Log out of the root account.

# exit

Change directory to /SD_CDROM. You see a lowercase listing of the directories and files on the CD-ROM. The mounted CD-ROM should appear as another read-only file system.

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 release earlier than 5.0, the system can contain undelivered messages that Oracle eMail Server 5.2 no longer processes. This is because the new release 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.
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 corrects the problem.
Do not put spaces in object names, use an underscore instead. This does not apply for descriptions or address lines.

For example, use John_Smith instead of John Smith.

Known Bugs

The following bugs 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, for example, 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 Oracle eMail Server release 5.2. This is necessary to ensure that the data in some of the replicator packages will not override other objects if applied after an upgrade has 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: If you are using Lotus Notes, sent messages are stored in the sent folder and the wastebasket.

The following bugs exist in the Thin Client:

1485419: You cannot open accounts with more than 1000 folders.
1532186: MSIE rich composer does not work on Macintosh platforms.
1403162: Netscape browsers sometimes print only the first visible page of information and not the entire message view.
1540468: Rules with name length of more than 80 characters cause problems
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 does not display high priority messages as high priority if received from the Thin Client. MS Outlook clients 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 email 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, Oracle 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 Internet File System (iFS) on the same system.

The iFS email component and the Oracle eMail Server both use Sendmail for mail transfer. However, iFS requires Sendmail Release 8.9.3 or later and eMail Server requires releases of Sendmail later than 8.
iFS ships an open source release of Sendmail 8.9.3. Windows NT and Windows 2000 based installations require Sendmail Release 3.0 or Sendmail Release 3.0.2 respectively.
iFS uses a post-installation script to configure the iFS email component. This includes setting up the Sendmail 8.9.3 executable and generating the generating the sendmail.cf file. For more information, refer to the Post-Installation steps in the iFS Installation Guide. To configure the sendmail.cf file for eMail Server, see Chapter 3, "Post-Installation," in the Oracle eMail Server Installation Guide.
iFS generates a new sendmail.cf file using its automated configuration script (ifsemailsetup). To have both the Oracle eMail Server and iFS working on the same system, you must incorporate the changes required for the Oracle eMail Server into the sendmail.cf file generated by the iFS setup scripts. You can do this only after the iFS configuation script has generated the sendmail.cf file. Note that the iFS setup script overwrites 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 system, they must be configured to run on different ports on that system.

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 requirements. For iFS, you can do this by running the iFS configuration utility. For Oracle eMail Server, you can do this through the Oracle 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.

Messaging Storage Parameters

During the Oracle eMail Server installation, there are 4 tablespaces created to accommodate e-Mail Server schema objects. The tablespace names are OFC_MESG, OFC_MAIN, OFC_INDB and OFC_INDS. These tablespaces are created with low extent values. All Oracle eMail Server schema tables and indexes in these tablespaces inherit their storage parameters from the tablespaces. There are several tables and indexes that grow rapidly and will require their next extent value to be increased as a post-installation task. Some of such these tables and indexes are listed below.

Note:

These tables are for internal use of eMail Server and must not be accessed directly.

Table	Associated Indexes
`OM_BODY`	`OM_BODY_KEY`
`OM_DATA`	`OM_DATA_KEY`
`OM_DATAE`	`OM_DATAE_KEY`
`OM_SHELL`	`OM_SHELL_KEY`
`OM_HEADER`	`OM_GLB_KEY` `OM_HDR_KEY` `OM_INCL_KEY`
`OM_EXT_HEADER`	`OM_EXT_KEY` `OM_EXT_PRUNE_KEY`
`OM_RECIPIENT`	`OM_RECIP_KEY` `OM_RECIP_NR_KEY`
`OM_INSTANCE`	`OM_INSTP_KEY` `OM_MSGUID_KEY` `OM_QUEUE_KEY` `OM_INST_RET_KEY`
`OM_FOLDER`	`OM_FLDR_KEY` `OM_FLDR_DK_KEY` `OM_FLDR_DC_KEY` `OM_FLDR_NAME_KEY`
`OM_FLDR_INSTANCE`	`OM_FLDR_INST_KEY` `OM_FI_PARENT_KEY`
`OM_DELAY`	`OM_DELAY_KEY`

Depending upon the size of your installation, select large next extent values to keep the total number of extents less than 1000 in a segment.

To change next extents on these tables and indexes do the following:

Run SQL*Plus as user OO_MAIL.
Run the following commands for each table and index listed above:
```
SQL> alter table table_name storage (next next_extent_value);
SQL> alter index index_name storage (next next_extent_value);
```
See Also:
For more information on storage parameters, refer to the Oracle8i Administrator's Guide.

Documentation Errors

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 )

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 Concepts Guide Release 5.2
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 the following URL: http://www.oracle.com/support