4
Oracle Email

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

• What's New in this Release?
• Known Issues
• Known Bugs
• Documentation Errata

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 9.0.2.3 and the Oracle9i Database 9.2.0.3. Several enhancements have been made to all components of the mail solution to improve performance and functionality. New features include:

• Improved virus scanning and protection, including an administration tool for quarantining messages suspected of virus infection in large stores; hands-off scanning of mail stores by third party anti-virus knowledge bases; and better virus scanning control for inbound and outbound mail.
• Per-user mail store backup and recovery, allowing backup and restoration of individual users' mail folders, private address book entries, and server-side rules.
• Network News Transfer Protocol (NNTP) server, providing threaded discussions and forum capabilities as well as an archive for Oracle Email public distribution lists.
• Migration Tool support for Novell GroupWise, version 6.0, and Samsung Contact, version 7.1 (formerly HP OpenMail).
• Additional features for the Oracle Connector for Outlook, including:
  • Delegated management of mail, allowing a user to assign someone else to temporarily manage one's mail
  • Additional server-side rules, including the popular "out of office" assistant
  • Support for message annotation
  • Flashback recovery of mail, allowing users to quickly recover deleted mail messages.

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

Workaround:

Enter the following command:

$ORACLE_HOME/ldap/bin/catalog.sh -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.

Workaround:

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:

   • CHINESE_VGRAM_LEXER
   • CHINESE_LEXER
   • JAPANESE_VGRAM_LEXER
   • JAPANESE_LEXER
   • KOREAN_LEXER
   • KOREAN_MORPH_LEXER.
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
    CTX_DDL.CREATE_PREFERENCE('my_lexer','LEXER_NAME');
   
    Create charset filter preference
    @ execute
   CTX_DDL.CREATE_PREFERENCE('my_charset_preference','CHARSET_FILTER');
    @ execute
    CTX_DDL.SET_ATTRIBUTE('my_charset_preference','charset','chosen_
   charset');
     chosen_char_set : Globalization support name of  source character 
   set.
   
    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
   FILTER        CTXSYS.CHARSET_FILTER
   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

Limitations:

• Indexing is limited to one lexer
• Indexing is limited to one 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
3029078	Administrator online help is missing. Workaround: None.
3028561	The es_mail schema does not have execute permission on lmmr_setup.setup_logmnr(). This prevents you from setting up LogMiner. Workaround: Log in as the SYS user on the mail story database and grant execute privileges on lmmr_setup to es_mail.
3032263	The text index synchronization task is not run by the housekeeping process. Workaround: None.
3036037	Housekeeper can fail with error ORA-6502 Workaround: None.
2978639	The orclguest user is not provisioned for e-mail, if the mail store configuration for first mail store fails. Workaround: To provision the orclguest account for e-mail, invoke the following script: $ORACLE_HOME/oes/bin/createEmailAccount.sh domain_name where: $ORACLE_HOME is the middle-tier oracle home domain_name is the e-mail domain
2882795	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.
2349530	You cannot install more than one email middle-tier on one machine.
2883242	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.
2972907	Search does not work with Oracle Email. Workaround: 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> <grantee> <codesource> <url>file:<middle_tier_oracle_ home>/ifs/files/lib/files.jar</url> </codesource> </grantee> <permissions> <permission> <class>oracle.security.jazn.JAZNPermission</class> <name>logon</name> </permission> </permissions> </grant>

4.3.1.1 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:

      (ENVS="EXTPROC_DLLS=<ORACLE_HOME>/lib32")
      
      

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
2918331	The orclmailnntpinboundpeers attribute must be cataloged after a middle-tier installation. The following command must be executed on the infrastructure machine $ORACLE_HOME/bin/catalog.sh -connect INFRA-SID -add -attr orclmailnntpoutboundpeers
2598308	The index is not available in the Help system. Keyword searches for help are not possible. Help content is available.
2841542	Migration tool throws OutofMemoryException while migrating users. Workaround: Edit migrate.cmd/migrate.sh script. Set the Minimum Heap(-Xms) to Max available heap. Edit the esmigration.config file in the %ORACLE_HOME%/oes/migration/config directory. Set oracle.mail.migration.num_of_threads to a lower value.

Table 4-3 Microsoft Exchange Plug-in

Bug No.	Description
2516725	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).
2558661	The plug-in fails to extract messages with embedded OLE objects.

Table 4-4 Lotus Domino R5 Plug-in

Bug No.	Description
2632809	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.
2991346	A few Traditional Chinese messages where the original character set is UTF-8 are not migrated properly.
2926772	During mailbox extraction, a "No Message File for Product=OES" message is logged.

Table 4-5 Novell GroupWise Plug-in

Bug No.	Description
2950698	Multibyte attachment names are not correct after migration (for Interpersonal messages).
2801219	The GroupWise plug-in does not extract Korean attachment names properly.
2794199	HTML body parts are not migrated properly for interpersonal mail.

Table 4-6 Samsung Plug-in

Bug No.	Description
2950501	Messages composed using non-standard clients may have corrupted headers.
2921831, 2921810, 2921793, 2921793, 2921763, 2921608	A few migrated messages are not properly displayed using Netscape 4.7x. Workaround: View the messages using Netscape 7.0 or Outlook Express.
2850889	Interserver messages after migration appear as extra attachments in Outlook Express. Workaround: 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
2990674	The IMAP sort command does not work correctly on profile folders.

Table 4-8 List Server Known Bugs

Bug No.	Description
2977691	Messages sent to the parent of nested external distribution lists are not archived for the child external list.
2675017	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.
2637279	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
2992003	The es.nntp.in.clients.total statistic is not being collected.
2988909	The anti-spam parameter Reject Connections from Host Domain(s)is not recognized by the NNTP Inbound server.
2991982	Articles containing a Distribution header value set for rejection are accepted. Only messages containing a Distribution header are affected.
2982508	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
2990786	Virus scrubber server and SMTP inbound server can crash if there is a space in the name of the external filter.
2988901	The anti virus pre-scan filter for the virus scrubber remains inactive when applied through the WebMail client administration pages. Workaround: Navigate to the Oracle Enterprise Manager Unified Messaging page. Select Virus Scrubber -> Default Settings. Enable the Pre-scan parameter.

4.3.4 WebMail

Table 4-11 WebMail Bugs

Bug No.	Description
3027830	Rules cannot be created through the WebMail client preferences page. Workaround: Set the value of the oracle.mail.sdk.esmail.encryption to false in the oc4j.properties file located in the $ORACLE_HOME/j2ee/OC4J_UM/config directory. Then restart the opmn processes.
3027752	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 Workaround: Click the Anti-virus or Anti-spam button to access the page.
2966292	JDK 1.4.1 or above must be used with WebMail to support GB18030 (Simplified Chinese PRC standard) encoding.
2899044	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

4.4.1.1 Chapter 2: Requirements Before Migration

• Preparing for a Novell GroupWise Migration:

  Novell Client Version 4.81 or higher should be installed on the system where the Migration Tool is installed.

• Choosing the Migration Option:

  Microsoft Exchange 5.0 and Microsoft Exchange 5.5 does not support Public Alias Migration from this Version.

• Preparing for a Microsoft Exchange Migration
  1. Create a profile.
  2. Check whether the Outlook Client is installed in Corporate or Work Group Mode.

  To check the mode in which the Outlook Client is installed:

  1. Open Microsoft Outlook.
  2. Click About Outlook under the Help option.
  3. If it is in Corporate or Working group, change nothing.
  4. If it is in Internet Mail Only Option, change the configuration from IMO to Corporate or Working Group Mode.
• To change the configuration of Microsoft Outlook from IMO to Corporate or Work Group mode:
  1. Click Tools On the Microsoft Outlook menu bar.
  2. Select Options > Mail Format> Reconfigure.
  3. Follow the wizard and select the Corporate or Working Mode radio button and finish.

     Note: Explicitly install the Microsoft Outlook 2000 client in Corporate Mode option if there are failures.

• After installation:
  1. Click Start > Control Panel > Mail.
  2. Click Show profiles.
  3. Click Add.
  4. Enter the appropriate information.
  5. Check whether the mailbox primary Windows NT account used in case of creation of a profile had the Service Admin or Admin role on the Exchange Server Machine. If not, add the NT user to the service admin accounts list using the Microsoft Exchange Administrator program.
  6. Stop and start the Exchange services to make permissions given take effect.
  7. Check if the Exchange Administrator program is installed on the machine.

4.4.1.2 Chapter 3: Migration Tasks

• If a forward slash (/) is present in a folder name, the Migration Tool replaces it with an underscore (_) and prefixes the folder with Renamed_.

  For example, if the original folder is named Sales/March, the name becomes Renamed_Sales_March.

• To Install the Migration Tool:

  ORACLE_HOME can be any directory on the machine from which the migration tool runs. It need not be a proper ORACLE installed ORACLE_HOME setup.

  Create a directory oes/migration under the set ORACLE_HOME.

• Task 8 - Migrating Distribution Lists

  Distribution lists are only created as SMTP distribution lists on Oracle. These can be converted to list server lists using the WebMail client administration pages.

  See Also: Oracle Email Administrator's Guide for more information on SMTP distribution lists and list server lists

4.4.1.3 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 userlistgen.sh from $ORACLE_HOME/oes/migration/bin.

   ./userlistgen.sh
   
   

   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.

   ./userlistgen.sh 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:

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

4.4.2 Oracle Email Application Developer's Guide

4.4.2.1 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.

     <grant> 
       <grantee> 
         <codesource> 
           <url>file:%JARFILE_NAME%</url> 
         </codesource> 
       </grantee> 
       <permissions> 
         <permission> 
           <class>oracle.security.jazn.JAZNPermission</class> 
           <name>logon</name> 
         </permission> 
       </permissions> 
     </grant> 
   
   

where:

$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,
cn=OracleContext)

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 

4.4.2.2 Directory Management Code Examples

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

jndi.jar, ldap.jar,  providerutil.jar, classes12.zip, $ORACLE_
HOME/jlib/repository.jar,  $ORACLE_HOME/jlib/esldap.jar, $ORACLE_
HOME/jlib/escommon.jar, $ORACLE_HOME/jlib/ojmisc.jar, $ORACLE_
HOME/j2ee/home/jazn.jar  

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

4.4.3 Oracle Email Administrator's Guide

4.4.3.1 Chapter 9: Parameters and Log Files

WebMail Properties

Table 4-12 WebMail Properties

Property	Description	Acceptable Values	Default Value
oracle.mail.sdk.esmail.driver_type	Determines the type of JDBC driver to be used for the database connection pool	oci8, thin (recommended in non-RAC)	oci8