Oracle Email Release Notes
Release 9.0.3

Part Number B10059-01
HomeSolution Area

Oracle® Email

Release Notes

Release 9.0.3

August 2002

Part No. B10059-01

1 What's New in this Release?

Oracle Email is now an integrated component of Oracle Collaboration Suite Release 1, Version 9.0.3. The product is certified to use Oracle9i Database Release 2 (9.2) database server as a message store.

This release includes the following new features:

2 Certification and System Requirements

This section describes the certification and system requirements for Oracle Email.

3 General Issues and Workarounds

This section describes general issues and workarounds for Oracle Email.

4 Configuration Issues and Workarounds

This section describes configuration issues and workarounds for Oracle Email.

4.1 Shutting Down Sendmail

On most UNIX systems, sendmail is configured by default and is started when the system comes up. To enable the Oracle Email SMTP server to listen to the default SMTP protocol port (port 25), sendmail must to be shut down. Execute the following command as root to shutdown sendmail:

/etc/init.d/sendmail stop

To prevent sendmail from restarting if the system is rebooted, remove the sendmail startup from the OS init files. If no other application running on that server uses it, rename the sendmail executable under /usr/lib.

4.2 Configuring Oracle Email with Multiple E-mail Domains

Oracle Email supports multiple e-mail domains on a single instance of the message store.

To add a new e-mail domain, perform the following steps:

  1. Create a new subscriber entry and associated directory information tree elements in Oracle Internet Directory.

The new subscriber objectclass and naming attribute can be configured per the customer's requirements.


Each Oracle Internet Directory subscriber required for an Oracle Email namespace is equivalent to an e-mail domain. To avoid confusion between e-mail subscribers and Oracle Internet Directory subscribers, the Oracle Internet Directory subscribers of the Object class domain are referred to as domains in this section. 

  • Create a new e-mail domain in Oracle Email and provision the users for e-mail access.

    4.2.1 Creating a new Domain in Oracle Internet Directory

    The directory administrator should use the following steps to create a new domain in Oracle Internet Directory:

    1. Determine the deployment-specific domain defaults:

    4.2.2 Provisioning Users in the New Domain with E-mail Access

    Once the new domain has been created in Oracle Internet Directory, create the associated e-mail domain and users through the Oracle Email administration tool.

    See Also:

    Chapter 3, of the Oracle Email Administrator's Guide 

    5 Known Bugs

    This section describes the known bugs for Oracle Email.

    5.1 Core Servers

    Table 1
    Bug No.  Description 


    The OESCHART $JAR environment is not set correctly. The correct $JAR environment setting is:



    The date format in advanced search is not localized. 


    The date format in messages is not in the local format.  


    In message replies, the encodings of the multibyte display name are displayed in the To line. 


    In the middle tier configuration, users can select a valid mail store from a drop down list. However, the first string of the drop down list is empty.

    Workaround: Expand the drop down list to view available mail stores. 


    The following folder names are not translated:

    • INBOX

    • Drafts

    • Sent

    • Sent Items



    The mailstore database must be registered with Oracle Internet Directory using netca or dbca. Because of the dbca bug, the database registration fails and unless the database is registered with Oracle Internet Directory, will fail. This happens on HP. 


    Due to the current limitation of Logminer in, it is not possible to recover messages larger than 4K .  


    If the action for a server-side rule moves the message to Inbox, the message is not considered processed, and subsequent rules process it again.  


    Configuring more than one mail store through the script logs following error in $ORACLE_HOME/oes/log/createmailstore.log:

    javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name

    This error can be ignored. 


    Not all rules can be removed.

    The API accepts undefined rules. Rules are grouped by events. Each event has a list of rules. If there is no rule defined for a particular event, then there should be no rulelist defined for that event. There cannot be an empty rulelist associated with an event. 


    The system, domain and user rules are not necessarily processed in a specific order.  


    The rule action "Move to INBOX" cannot keep a message in the INBOX if the message also subject to other rule actions as well.

    If a rule performing the action "Move to INBOX" is created, a message performing this action (been kept in INBOX) can be moved by other actions such as "Move to folder1," if the message warrants both actions. However, if move to folder1 is performed first, the message is kept in folder1 for the duration of all the rules execution and is not subject to further moves regardless of how many more rules this message qualifies.

    Workaround: Do not use INBOX as a move destination, use a regular folder instead. An OJMA SDK user can also programmatically insert a "break" action immediately after "move to Inbox" action to prevent further rules from being executed. 


    Two users with the same user ID in different domains cannot create a shared folder with the same name. 


    The portlet cannot retrieve the SSO user DN in Oracle Internet Directory. 


    Shared folders that have too many levels of nested folders cannot be created. The number of levels of shared folders that can be created successfully depends on various factors, such as the string length of domain name, the string length of the user ID, and the string length of each folder name. Based on these factors, the maximum number of shared folder hierarchies that can be created can vary from installation to installation. 


    The OracleText index for message search is created in the system tablespace by default.

    The following example describes how to create an index in a user-selected tablespace:

    1. Create a tablespace:

      CREATE TABLESPACE esoratext 
          DATAFILE '?/dbs/esoratext.dbf' SIZE 100M 
              AUTOEXTEND ON 
              NEXT 10M 
              MAXSIZE UNLIMITED 
    2. Drop the OracleText index and recreate the index using this tablespace. To use the tablespace, add a STORAGE your_desired_tablespace clause to the parameter list of the index creation statement.

      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'); 

    See Also: OracleText Reference for more information on index creation 

    5.2 Protocol Servers

    Table 2
    Bug No.  Description 


    The protocol server hangs when it cannot create more database sessions. This issue occurs if the maximum connection pool parameter in the protocol server is set to a value greater than the maximum sessions allowed for the mail store database. 


    The default domain parameter is not set during installation. During login, if administrators want users to specify only their user ID and not the fully qualified user ID and domain name, set the default domain parameter to the IMAP server. 


    When the IMAP server timeout interval parameter is modified, the server must be restarted, not reinitialized. 


    When the Oracle Internet Directory is down, the SMTP server sends an invalid recipient error to the client, instead of a temporary error with a clear description. 

    5.3 Thin Client

    Table 3
    Bug No.  Description 


    The Administration tool Goto Directory Create User Screen redirect button does not work.

    Administrators must manually enter the Delgated Administration Service (DAS) URL. 


    The rich text compose screen has been coded to standard 508, but we are aware of several usability issues for users dependent on assistive technologies because of third party dependencies.

    Oracle Corporation provides a patch on request to circumvent these usability issues.

    These issues include:

    • non spoken input fields for messages

    • non tab-able edit icons in the composer toolbar

    • inability to use formatting functionality through keystrokes

    • non spoken browse buttons for uploading files



    If the number of messages exceeds the page size, the messages are shown one page at a time. If the user is viewing the last page, and selects and deletes all messages, the page index is not reset and the user is presented with the message error "Folder is empty." However, the drop-down to select other pages of the folder is still correct.

    Workaround: Perform one of the following returns the mail session to a valid state:

    • Use the drop-down to select other pages of the folder to correctly present the messages.

    • Use the "Previous 10" link to correctly taks the user to the previous page of messages



    The shared folders options section is not translated. 


    In several Thin Client pages, the skip navigation link is not working properly with assistive technology.

    Workaround: Disable the virtual cursor mode by pressing insert + z. The skip navigation links work properly after this.  


    The message priority options (normal and high) are not translated. 


    The invalid date error message is not translated. 


    The message size bytes value is not translated. 


    The send date condition may not work for non English languages. 


    The English and user interface translations do not match. 


    Languages are not in English, if the default SSO language is set to something other than English. 


    When creating a new Oracle Collaboration Suite base user, an e-mail address is required to be associated with this user by DAS even though the e-mail account for this user has not been created yet.

    This e-mail address is stored as the first entry in an array of e-mail addresses in the base user object for this user. When an e-mail account is created for this user, an e-mail address is also created for this user as well. This new e-mail address is also added to the base user object array of e-mail addresses, but it is appended to the array rather than replacing the first item or reshuffling the array in order to be placed at the top.

    Previously, the Thin Client only looked at the first address in the array and tried to log into that account. Because this address was specified during the DAS user creation, there was no guarantee that this was a valid Oracle Collaboration Suite account.

    The Thin Client utilizes a server API to query for all valid e-mail addresses and tries to log into the first one of this subset.

    For example, if during the DAS user creation, the administrator specifies a valid e-mail address for Oracle Collaboration Suite, and if the e-mail address specified has the correct domain in the e-mail address for this Oracle Collaboration Suite installation, even if no account is associated with it, this e-mail address is still the first item in the set of addresses returned by the new APIs. This causes the Thin Client to log into the wrong e-mail address.

    To address this, administrators have to be careful about specifying what e-mail address is entered when creating a user through the DAS HTML UI user creation pages, so that it is the same address that is eventually used by e-mail server. If the "invalid but valid looking" e-mail address is already in place, the adminstrator must use Oracle Internet Directory tools to manually update the base user object's array of e-mail addresses. 


    The All Folders page has an icon to expand or compress folder trees. After executing this function the focus is returned to the top of the page.  


    The inbox can be sorted ascending or descending, but the arrow link indicating this is not clear. Instead the screen reader says "javascript colon sort ... " 

    2452291 & 2452268 

    In Address Book Advanced Search, there is an attribute for searching called Entry. This attribute refers to the distribution list or alias of contact name of the entry. 


    If a message with automatically generated messages with malformed content is sent, there is a possibility that the attachment cannot be opened. 


    If a filter is created specifying a folder name, subsequent modifications of the folder name do not update the rule. The rule points to a non-existent folder. 


    If a rule is created to notify the user upon deletion of a message, two notifications are sent if the preference for message deletion is set to send to Wastebasket, instead of removing it completely. 


    Filters utilize case sensitive matches, and if non case sensitive matches are needed, multiple rule criterias are currently required. 


    Attachments within template messages is not available. 


    Folders containing special characters cannot be expanded. This only affects expanding the folder in the folder list view and does not prevent the user from accessing this folder by other means. 


    When a message containing an inserted image is forwarded, the image is corrupted. 


    Sent messages are not copied into the sent folder when users are over quota. 


    It is possible for malformed HTML content to be contained within an automatically generated e-mail message. If a message with automatically generated messages with malformed content is sent, there is a possibility that an error displays when viewed through the Thin Client. 


    Internet Explorer 5 crashes when the address book table is sorted by column. 


    An error message is displayed when shared folders are compacted. 


    When creating a list, if a name is not specified, a Java exception is thrown and displayed in the folder description box. Although the user can still create the list by entering a name for the list, they must remember to edit the description to remove the exception string. 


    When a duplicate list is created, the error message displayed is unclear. 


    In the Address Book simple search, there is a search attribute called "Number" and that is unclear to the end user. This number refers to the "Work Phone Number" because this is the number used for searching. 


    When a duplicate contact name is created, the error message displayed is unclear. 


    The search results table does not display unread messages in bold. 


    The breadcrumb links prevents users from navigating back to the search results list when viewing a specific item from the list of search results. 


    Various error messages generated from modifying a folder generate a screen that does not have a way to close and return to the previous view. The workaround is to use the back button in the browser and refresh the previous page. 


    Internet Explorer 5 crashes intermittently when messages are sorted according to size. 


    When deleting a message in the message view, the message becomes corrupted. 


    An over quota message is not displayed when logging into an account that is over quota. 


    When a new directory contact is created, the fields are not validated. 


    The Multi-byte display name and subject are corrupt in the notification. 


    The Thin Client corrupts both the auto-reply subject and text lines. 


    An e-mail user with a multi-byte user ID cannot log in to the Thin Client. 

    5.4 Third Party Clients

    Table 4
    Bug No.  Description 


    In Netscape 4.7 x, folders with spaces in the name cannot be expanded.

    The workaround is to rename a folder. 


    Netscape 4.75 does not support the DHTML components required to provide a rich text editor 


    In Netscape Messenger 4.7, POP3 users cannot log in. 

    Oracle is a registered trademark of Oracle Corporation, and Oracle9i, Oracle Store, PL/SQL, and SQL*Plus are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.

    Copyright © 2002 Oracle Corporation.

    All Rights Reserved.

  • Oracle
    Copyright © 2002 Oracle Corporation.

    All Rights Reserved.
    HomeSolution Area