IBM Email Manager 3.7.1 Fix Pack Readme: 3.7.1.8-EM-FP008

Readme file for: IBM Email Manager
Product/Component Release: 3.7.1
Update Name: Fix Pack 8
Fix ID: 3.7.1.8-EM-FP008
Publication date: 24 March 2010
Last modified date:

Contents:

About this fix pack:
Download location
Required products needed before installation
Known issues
Prerequisites and co-requisites

Installation information:
  Prior to installation
  Installing
  Uninstalling if necessary

List of fixes
Additional information
Copyright and trademark information
Document change history

Download location:

Download Email Manager Version 3.7.1 Fix Pack 8 (3.7.1.8-EM-FP008) from the following location:
Fix Central site: http://www.ibm.com/support/fixcentral New!

Select Product Group: Information Management
Select Product: FileNet Email Manager

Below is a list of products/components names, platforms, and file name(s) that apply to this readme file.

Product/Component Name:	Platform:	File Name:
Server	Windows	emserver_371-008.exe
Client	Windows	emclient_371-008.exe

Required products needed before installation:

Product/Component Name:	Platform:
Email Manager 3.7.1 Service Pack 1	Windows

New in this fix pack:

As of EM 3.7.1 Patch 7 (3.7.1.7-EM-FP007) the following components are supported:

· Image Services 4.1.2

· Content Services 5.5

Known issues:

Defect No.

Description

ecmdb00749112

In the readme for EM 3.7.1 it states "The following component must be installed before installing this service pack: * EM-3.7.0 (Email Manager 3.7.0 GA)"

When attempting to do a silent install using the MSI, the error message "another version of this product is already installed" is displayed. To perform a silent install of 3.7.1, you must first uninstall 3.7.0.

Installation information:

Prior to installation:

1. Back up the EM database

Installing this patch:

1. Extract the fix pack zipped file to the local file system.

2. Stop the following Email Manager services (if installed):

· eMgr PST Connector

· eMgr Exchange Connector

· eMgr Lotus Connector

· eMgr GroupWise Connector

· eMgr Universal File Importer

3. Stop the Internet Information Services (IIS) default website or Application Pool where the Email Manager Web services are installed.

4. Stop the following IIS related services:

· IIS Admin Service

· World Wide Web Publishing Services

5. Stop any other applications that are running, including the Email Manager Configuration Manager.

6. In the directory where the zip file was extracted access the folder "EM Server Patch" and run: emserver_371-008.exe

7. When prompted to upgrade click 'Yes'. At the installation start screen click 'Next' to start the installation. Updated Email Manager Server components will now be installed.

8. Start the following Email Manager services (if installed):

· eMgr PST Connector

· eMgr Exchange Connector

· eMgr Lotus Connector

· eMgr GroupWise Connector

· eMgr Universal File Importer

9. From the command prompt, run the following command to re-start IIS related services: iisreset

Installing the Email Manager Client fix pack manually:

1. Extract the fix pack zipped file to the local file system.

2. Close the email client application (Outlook or Lotus Notes or GroupWise).

3. In the directory where the zip file was extracted access the folder "EM Client Patch" run: emclient_371-008.exe

4. When prompted to upgrade click 'Yes'. At the installation start screen click 'Next' to start the installation. Updated Email Manager Client components will now be installed.

5. Changes were made to the DXL Viewer in EM-3.7.1-002. If you have not installed EM-3.7.1-002 and you wish to update the DXL Viewer components, you must manually copy the new style sheets provided in the StyleSheets folder in the patch to the StyleSheets folder on every machine where the DXL Viewer has been installed. The StyleSheets folder is typically located at “C:\Program Files\FileNet\Email Manager Client 3.7\StyleSheets”. The following is a list of the style sheets that must be copied: DXLViewer.xsl, DXLViewerCore.xsl, DXLViewerScript.xsl, DXLViewLinks.xsl, DXLViewMail.xsl and DXLViewProperties.xsl2.

Installing the Email Manager Client fix pack silently:

For scripted silent installs of the Email Manager Client fix pack, the fix pack can be run in a batch file using the following syntax:

emclient_371-008.exe /S /V"/qn INSTALLPDBFILES= 1"

Note that to update the DXL Viewer, the steps in #5 (Install the Email Manager Client fix pack manually) above are still required.

Uninstalling this patch:

1. In Add/Remove Programs, remove FileNet Email Manager Client 3.7

2. In Add/Remove Programs, remove FileNet Email Manager Server 3.7

3. Restore the EM database from backup

4. Install FileNet Email Manager Server 3.7.1 Service Pack 1 from Email Manager GA media

List of fixes:

APAR No.	Defect No.	Severity	Abstract
PJ37523	ecmdb00850353	2	THE VALUE FOR TEXT PROPERTY IN EMAIL MANAGER CLIENT PROFILE CANNOT BE SAVED IF EXCEEDING 255 CHARACTERS
PJ37522	ecmdb00853671	2	IS MENU ITEM PROPERTY IS NOT WORKING PROPERLY IF THERE ARE MULTIPLE MENU ITEM PROPERTIES DEFINED IN THE CLIENT PROFILE
PJ37410	ecmdb00851663	1	LOTUS CONNECTOR DOES NOT RECOGNIZE MIME ATTACHMENT IN EASYLINK FAXCOURIER MESSAGES

Additional Information:

As of EM 3.7.1 Patch 7 (3.7.1.7-EM-FP007)

Items

Descriptions

Error items are copied into the error folder repeatedly if post-processing is set to delete

The current behaviour in Email Manager is to not mark an email as processed if post-processing options are set to delete. In this situation, an error item that is not captured is not marked as processed and will be copied to the error location each time the collector polls that monitored location. To change this behaviour, create a registry entry in the following path:

HKEY_LOCAL_MACHINE\SOFTWARE\FileNet\Email Manager\3.7\Settings\

Key Name: MarkErrorAsProcessed

Type: DWORD

Values: 0 - the default behavior occurs and error emails will not be marked as processed and on every poll it will be

copied into the error folder.

1 - this will mark error files as processed so they do not move into the error folder repeatedly

Emails received from an outside source have their Email Manager “From” field mapped from the “SMTPOriginator” in the notes message

Add a registry key that controls the source of the From email address. If set, it changes the default behaviour and uses From instead of SMTPOriginator

Create a registry entry set in the following path:

HKEY_LOCAL_MACHINE\SOFTWARE\FileNet\Email Manager\3.7\Settings\LotusConnector

Key Name: UseSMTPOriginator

Type: DWORD

Values: 0 - always use From

1 - Use SMTPOriginator (default)

Recovering from a Lotus Panic Attack

Lotus Connector - Lotus Notes Panic detection

The Lotus Connector now includes a feature for Lotus panic detection. A Notes panic is a forced termination of one or more Notes processes. When a panic occurs, the Lotus Connector hangs as Domino COM API remote procedure calls do not return to the calling application.

The panic detection feature performs the following:

- Monitoring the Lotus Notes console log file for Notes panic events.

- Logging the Notes messages that were being processed at the time the panic occurred.

- Automatically terminating Notes processes using .nsd -kill

- Automatically restarting the Lotus Connector service.

- Skipping message IDs logged in the panic log file to prevent recurring panics caused by corrupt messages.

The panic log file records the message location and universal Id of the message, allowing the message to be located for troubleshooting. If the message has been opened, the log also records the subject of the message. The log also records in-progress activities that are known to cause an elevated risk of Notes panics, such as DXL export.

Sample panic log file:

<?xml version="1.0" encoding="utf-8"?>

<server>CN=server1/O=acme</server>

<dbpath>mail\wileecoyote</dbpath>

<view>ACME\Dynamite</view>

<subject>Re: Protect from naked flame</subject>

<riskactivity>DXLExport</riskactivity>

</document>

<server>CN=server1/O=acme</server>

<dbpath>mail\wileecoyote</dbpath>

<view>ACME\Dynamite</view>

<subject>Fw: Cleaning blackened face after mis-using product</subject>

<riskactivity>DXLExport</riskactivity>

</document>

<server>CN=server1/O=acme</server>

<dbpath>mail\wileecoyote</dbpath>

<view>ACME\Anvils</view>

<subject>New! Now even heavier...</subject>

</document>

<server>CN=server1/O=acme</server>

<dbpath>mail\bugsbunny</dbpath>

<view>ACME\Anvils</view>

</document>

</incident>

</panicdetection>

Registry entries controlling Panic detection

Path: HKEY_LOCAL_MACHINE\Software\FileNet\Email Manager\3.7\Settings\LotusConnector

Key Name: PanicLogFolder

Type: String

Value: Folder where panic log files will be saved. If supplied, must be a valid file system folder. If this registry entry does not exist, panic log files are written to the EMM log file folder.

Key Name: PanicLogFile

Type: String

Value: File name (including extension) to use for the panic log file. If this registry entry does not exist, defaults to PanicLog.Xml

Key Name: PanicRestart

Type: DWORD

Values: 0 - disables automatic restart on panic detection

1 - enables automatic restart.

If this registry entry does not exist, automatic restart on panic detection is enabled.

Handling messages where the subject and attachment names contains characters outside the ASCII range

There are three registry entries that control how EM names files. Although intended for IS, this feature is also compatible with CS and P8.

All registry settings are set in the following path:

HKEY_LOCAL_MACHINE\Software\FileNet\Email Manager\3.7\Settings\LotusConnector

Key Name: UseAsciiFilenames

Type: DWORD

Values: 0 - disabled

1 - enabled

If enabled, enables special handling for characters outside the normal ASCII range in both subjects and attachment names. When enabled, non-ASCII characters are converted to underscores, unless used in conjunction with the following registry entries.

Key Name: NonAsciiSubjectText

Type: String

Value: If set, the value entered here will be used in place of the subject when generating a filename for messages

where the subject contains characters outside the ASCII range. This behaves in a similar way to the

null subject text used for messages that do not contain a subject. Do not include any characters that are invalid

in filenames (e.g.: \ *? etc.).

Key Name: NonAsciiAttachmentText

Type: String

Value: If set, the value entered here will be used in place of the attachment filename when the attachment filename

contains characters outside the normal ASCII range. Do not include any characters that are invalid in

filenames (e.g.: \ *? etc.).

This feature will allow processing of the client queue backlog.

Since IS does not support zero byte files use a placeholder to bypass this limitation

When attempting to capture Lotus Notes attachments to IS, the capture attempt will fail if the message contains zero byte attachments, as IS does not support zero byte files - this is an IS limitation. The IS connector is aware of this limitation and throws an exception (because of a problem in the exception handling, the exception that is logged is a rather cryptic serialization error, making diagnosis difficult).

EM 3.7.1-007 contains an enhancement to work-around this problem. If this feature is enabled, the zero-byte file is replaced with the contents of a place-holder file, and the file extension of the exported file is modified to match the place-holder file so that the file associations work correctly. The placeholder file may be of any size or type, but will typically be either a small text file or a small image file to indicate that the original file was a zero-byte attachment. The attachment metadata is unchanged when the place-holder file is used.

Although intended for use with IS, this feature can also be used with CS and P8 repositories.

This feature is enabled by the following registry entry:

Path: HKEY_LOCAL_MACHINE\Software\FileNet\Email Manager\3.7\Settings\LotusConnector

Key Name: ZeroByteAttachmentPrototype

Type: REG_SZ (string)

Value: Filename (including full or relative path) of the place-holder file to use.

If the file is not found, a warning message will be written to the log and the connector will revert to the existing behaviour. Trace messages are also written to the log when zero byte attachments are found and processed.

Copyright and trademark information:

http://www.ibm.com/legal/copytrade.shtml

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY  10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law

IBM Japan, Ltd.

3-2-12, Roppongi, Minato-ku, Tokyo 106-8711 Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation

J46A/G4

555 Bailey Avenue

San Jose, CA  95141-1003

U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

Trademarks

· IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

· Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

· Microsoft, Windows, Windows NT, SQL Server, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

· UNIX is a registered trademark of The Open Group in the United States and other countries.

· Other company, product, or service names might be trademarks or service marks of others.

THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.

Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions:

The Excluded Components are provided on an "AS IS" basis
IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
IBM will not be liable to you or indemnify you for any claims related to the Excluded Components
IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.

Document change history: