Skip Headers

Oracle Collaboration Suite Release Notes
Release 2 (9.0.4) for hp-ux PA-RISC (64-bit) and Linux x86

Part Number B12029-02
Go To Table Of Contents

Go to previous page Go to next page

Oracle Email

This chapter summarizes release note issues associated with Oracle Email. The following sections are included in the chapter:

4.1 What's New in this Release?

Release 2 of the Oracle Collaboration Suite e-mail product ships with restricted use licenses for the Oracle9i Application Server and the Oracle9i Database Several enhancements have been made to all components of the mail solution to improve performance and functionality. New features include:

4.2 Known Issues

This section describes Oracle Email known issues.

4.2.1 TargetDN Attribute

The targetdn attribute must be cataloged manually. If this attribute is not cataloged, the user rename operation fail


Enter the following command:

$ORACLE_HOME/ldap/bin/ -connect infrastructure_connectstr -add \
-attr targetdn

See Also:

Bug number 2437872 for more information.

4.2.2 Oracle Text

Text index for e-mail body search is created with the Oracle Text BASIC_LEXER, which supports English and most western European languages that use white space delimited words. For other languages that are not supported by Oracle Text BASIC_LEXER, e-mail body search does not work.


  1. Enter the following SQL command:

    SQL> alter table es_imt_msgbody add (cset VARCHAR2(20) default 'JAAUTO');
  2. Choose a lexer for e-mail indexing.

    Supported lexers are:







  3. As the es_mail database user, drop the existing index es_ot_ix_search file. This causes all previously indexed e-mails to be un-indexed.

  4. Recreate the index es_ot_ix_search file with the lexer chosen in step 2. This causes all previously indexed e-mails to be re-indexed using the new lexer.

  5. Determine whether tablespace esoratext exists.

  6. Run the following SQL as database user es_mail to recreate the index:

    @ execute
     Create charset filter preference
     @ execute
     @ execute
      chosen_char_set : Globalization support name of  source character 
     DROP INDEX es_ot_ix_search;
     CREATE INDEX es_ot_ix_search ON es_imt_msgbody(text)
             indextype IS ctxsys.context
             parameters ('DATASTORE es_search_dspref
    SECTION GROUP  es_search_sec_group
    STORAGE               oratextstore
    LEXER          my_lexer
    CHARSET COLUMN cset') ;
  7. Replace the following entries as described:

    • my_lexer with a unique name

    • LEXER_NAME with the name of the chosen lexer

    • my_charset_preference with an unique name

    • chosen_charset with the name of the source character set


4.3 Known Bugs

This section describes the known bugs for Oracle Email.

4.3.1 Administration

Table 4-1 Administration Known Bugs
Bug No. Description


Administrator online help is missing.




The es_mail schema does not have execute permission on
lmmr_setup.setup_logmnr(). This prevents you from setting up LogMiner.


Log in as the SYS user on the mail story database and grant execute privileges on lmmr_setup to es_mail.


The text index synchronization task is not run by the housekeeping process.




Housekeeper can fail with error ORA-6502




The orclguest user is not provisioned for e-mail, if the mail store configuration for first mail store fails.


To provision the orclguest account for e-mail, invoke the following script:

$ORACLE_HOME/oes/bin/ domain_name


  • $ORACLE_HOME is the middle-tier oracle home

  • domain_name is the e-mail domain


System rules for message delivery can be invoked more than once for a message, if the message delivery fails during the first delivery attempt and delivery is tried again.


You cannot install more than one email middle-tier on one machine.


When enabling the distribution list synchronization option from administration pages, the list of objectclass names must contain the groupofuniquenames or groupofnames explicitly, even if the objectclass definition is inherited.


Search does not work with Oracle Email.


On all Oracle mid tier environments, edit the
$ORACLE_HOME/oes/jazn/jazn-data.xml file to include the following text immediately before the line containing /jazn-policy. Replace the middle_tier_oracle_home in the following text with the full directory path for ORACLE_HOME

  </grant> HP-UX Only: Email Component Issue and Database Listener

On HP-UX, the database listener must be configured to use extproc32 for external procedure agent callout.

To configure:

  1. Modify the Information Storage listener.ora file, as follows:

    1. Set the program parameter to extproc32 instead of extproc as follows:

      (program = extproc32)
    2. Add the following line:

  2. Set the SHLIB_PATH environment variable, as follows:

    • For the Bourne, Bash, or Korn shell enter:

      $ export SHLIB_PATH=$ORACLE_HOME/lib32
    • For the C shell enter:

      setenv SHLIB_PATH $ORACLE_HOME/lib32
  3. Restart the listener.

4.3.2 Migration

Table 4-2 Migration Tool Known Bugs
Bug No. Description


The orclmailnntpinboundpeers attribute must be cataloged after a middle-tier installation. The following command must be executed on the infrastructure machine

$ORACLE_HOME/bin/ -connect INFRA-SID -add -attr orclmailnntpoutboundpeers


The index is not available in the Help system. Keyword searches for help are not possible. Help content is available.


Migration tool throws OutofMemoryException while migrating users. Workaround:

  1. Edit migrate.cmd/ script.

  2. Set the Minimum Heap(-Xms) to Max available heap.

  3. Edit the esmigration.config file in the %ORACLE_HOME%/oes/migration/config directory.

  4. Set oracle.mail.migration.num_of_threads to a lower value.

Table 4-3 Microsoft Exchange Plug-in
Bug No. Description


The Microsoft plug-in does not extract a shared folder from the Microsoft Exchange server if the shared folder does not have an owner, or if the default permission for that folder is not defined.

Workaround: Verify that all folders have owners and the default permission defined before migrating them into the Oracle Email (See bug 2516792).


The plug-in fails to extract messages with embedded OLE objects.

Table 4-4 Lotus Domino R5 Plug-in
Bug No. Description


Unable to open some attachments using Netscape 4.x after MBOX based migration with NLS messages.

Workaround: View using Netscape 7.0 or Outlook Express.

2558661, 2827041

Embedded images and Notes Rich Text Format are not migrated from Lotus (for Interpersonal messages only).

2775294, 2760551

Format information is lost for Mulipart/Parallel and Multipart/Singed message types.


A few Traditional Chinese messages where the original character set is UTF-8 are not migrated properly.


During mailbox extraction, a "No Message File for Product=OES" message is logged.

Table 4-5 Novell GroupWise Plug-in
Bug No. Description


Multibyte attachment names are not correct after migration (for Interpersonal messages).


The GroupWise plug-in does not extract Korean attachment names properly.


HTML body parts are not migrated properly for interpersonal mail.

Table 4-6 Samsung Plug-in
Bug No. Description


Messages composed using non-standard clients may have corrupted headers.







A few migrated messages are not properly displayed using Netscape 4.7x. Workaround: View the messages using Netscape 7.0 or Outlook Express.


Interserver messages after migration appear as extra attachments in Outlook Express.


Set INET_INLINE_FNAME_ALLOWED=FALSE in the general.cfg file in /var/opt/openmail/sys on the source Samsung Contact server before MBOX generation.

If the option is set to FALSE, all the inline body parts will not have filename= in the Content-Disposition line even if a file name exists.

4.3.3 Servers

Table 4-7 IMAP Server Known Bugs
Bug No. Description


The IMAP sort command does not work correctly on profile folders.

Table 4-8 List Server Known Bugs
Bug No. Description


Messages sent to the parent of nested external distribution lists are not archived for the child external list.


Data returned by a PL/SQL function for a mail-merge tab is not translated into the character set of the e-mail into which the data is inserted.


If an alias is made a member of a mailing list and a mail with mail-merge tags is sent to such a list, then the mail-merge will be incorrect for the alias recipient. All other normal users are unaffected.

Table 4-9 NNTP Server Known Bugs
Bug No. Description


The statistic is not being collected.


The anti-spam parameter Reject Connections from Host Domain(s)is not recognized by the NNTP Inbound server.


Articles containing a Distribution header value set for rejection are accepted. Only messages containing a Distribution header are affected.


The oespr utility does not allow multiple outbound peers for a group to be set. The peer name is replaced with the new value instead of appending the new value, so that a newsgroup can be fed to one peer only.

Table 4-10 Virus Scrubber Known Bugs
Bug No. Description


Virus scrubber server and SMTP inbound server can crash if there is a space in the name of the external filter.


The anti virus pre-scan filter for the virus scrubber remains inactive when applied through the WebMail client administration pages.


  1. Navigate to the Oracle Enterprise Manager Unified Messaging page.

  2. Select Virus Scrubber -> Default Settings.

  3. Enable the Pre-scan parameter.

4.3.4 WebMail

Table 4-11 WebMail Bugs
Bug No. Description


Rules cannot be created through the WebMail client preferences page.


Set the value of the oracle.mail.sdk.esmail.encryption to false in the file located in the
$ORACLE_HOME/j2ee/OC4J_UM/config directory. Then restart the opmn processes.


If you click the Policy tab, the following incorrect error message appears, even if you have system administrator privileges:

You do not have permission to access this page


Click the Anti-virus or Anti-spam button to access the page.


JDK 1.4.1 or above must be used with WebMail to support GB18030 (Simplified Chinese PRC standard) encoding.


WebMail online help is not context sensitive.

4.3.5 Multi-Byte Character Restrictions in Netscape Navigator

Multi-byte characters are sometimes not displayed properly. Oracle assigned bug number 2354956 to track this. If this problem occurs, do the following:

  1. From browser menu, click Edit and Preferences.

  2. Select Fonts within Appearance from Category.

  3. Select "Use my default fonts, overriding document-specified fonts".

  4. Click "OK" and access again.

4.4 Documentation Errata

4.4.1 Oracle Email Migration Tool Guide Chapter 2: Requirements Before Migration Chapter 3: Migration Tasks Appendix C

Userlistgen generates the users.xml file for IMAP-based migration where the passwords are protected. This file is used by the Migration Tool for loading users.

  1. Run from $ORACLE_HOME/oes/migration/bin.


    The Migration Tool reads the following parameters from Standard input. To terminate, press ENTER twice.

    For example:

    sourceimapuserid=test1 sourceimappasswd=welcome1 targetimapuserid=test1
    targetimapuserpasswd=welcome1 quota=50 sourceimapuserid=.....

    When this is complete, the users.xml file has to be copied to the required directory from where the Migration Tool will read it.

    ./ file=<name> 

    The Migration Tool reads the file (in the users.xml format supported by the Migration Tool) and the output file is generated in the same directory with the passwords in the users.xml file protected.

    For example: for input file:

    <user sourceimapuserid="test1" sourceimappasswd="welcome1"
    targetimappasswd="welcome1" quota="10" />

4.4.2 Oracle Email Application Developer's Guide Chapter 2: Java API Reference

Directory Management API: Directory Components

Before a caller can access any of the directory components, the caller must authenticate with the LDAP directory using the oracle.mail.OESContext class. Once authenticated, the instance of oracle.mail.OESContext representing a trusted session must be passed to all of the directory APIs. There are two ways of authenticating: in the middle-tier ORACLE_HOME and by providing the user credentials.

Authentication in the Middle-Tier Oracle Home

In this authentication model, the application must be deployed on a middle-tier host.

The $ORACLE_HOME/oes/jazn/jazn-data.xml file must be modified as described below.

  1. Back up the original $ORACLE_HOME/oes/jazn/jazn-data.xml file.

  2. Open $ORACLE_HOME/oes/jazn/jazn-data.xml

  3. Go to the end of the file.

  4. Before the </jazn-policy> tag, add the following lines.



$ORACLE_HOME is the Oracle home path in the middle-tier host

%JARFILE_NAME% is the absolute path of the application jar file.

Example authenticating as an application with the debug option turned off

OESContext oesctx = new OESContext(DirectoryConstants.DS_CALLERTYPE_APP, false); 
//Authenticate to the directory 
oesctx.authenticate(null, oracle_home); //oracle_home is the oracle home path on 
the middle tier host 
Authentication Providing Super User Credentials

In this authentication model , the application must provide Oracle Internet Directory super user credentials (credential of cn=orcladmin or cn=umadmin,cn=EmailServerContainer,cn=Products,

Example authenticating as an application passing super user credentials with the debug option turned off

OESContext oesctx = new OESContext(DirectoryConstants.DS_CALLERTYPE_APP, false); 
//Authenticate to the directory 
oesctx.authenticate(username, password, ldaphost, ldapport); //username - super 
user dn, password - super
user password, ldaphost - OID host name, ldapport - OID port number Directory Management Code Examples

To run these examples, the CLASSPATH environment variable must include the following:

jndi.jar, ldap.jar,  providerutil.jar,, $ORACLE_
HOME/jlib/repository.jar,  $ORACLE_HOME/jlib/esldap.jar, $ORACLE_
HOME/jlib/escommon.jar, $ORACLE_HOME/jlib/ojmisc.jar, $ORACLE_

The $ORACLE_HOME/oes/jazn/jazn-data.xml file must be edited as described above.

4.4.3 Oracle Email Administrator's Guide Chapter 9: Parameters and Log Files

WebMail Properties
Table 4-12 WebMail Properties
Property Description Acceptable Values Default Value


Determines the type of JDBC driver to be used for the database connection pool

oci8, thin (recommended in non-RAC)


Go to previous page Go to next page
Copyright © 2002, 2003 Oracle Corporation.

All Rights Reserved.
Go To Table Of Contents