emailxtender - axantech.com · snapshotserver, quikstartz, alphastor, clientpak, xtender,...

March 2, 2005

EmailXtender®

Release 4.7

Release Notes

Copyright © 2005 by EMC Corporation. All rights reserved. This software (including documentation) is subject to the terms and conditions set forth in the end user license agreement or other applicable agreement, and you may use this software only if you accept all the terms and conditions of the license agreement. This software comprises proprietary and confidential information of EMC. Unauthorized use, disclosure, and distribution are strictly prohibited. Use, duplication, or disclosure of the software and documentation by the U.S. Government are subject to restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer Software - Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is LEGATO Software, a division of EMC, 2350 West El Camino Real, Mountain View, CA 94040.

EmailXtender Release Notes

March 2, 2005

e4-1881-01

LEGATO and the LEGATO logo are registered trademarks, and LEGATO NetWorker, NetWorker, AAM, Co-StandbyServer, RepliStor, SnapShotServer, QuikStartz, AlphaStor, ClientPak, Xtender, XtenderSolutions, DiskXtender, ApplicationXtender, ArchiveXtender, EmailXtender, and EmailXaminer are trademarks or registered trademarks of LEGATO Software, a division of EMC. This is a nonexhaustive list of LEGATO trademarks, and other trademarks may be the property of their respective owners.

The following may be trademarks or registered trademarks of the companies identified next to them, and may be used in this document for identification purposes only.

Acrobat, Adobe / Adobe Systems, Inc.Apple, Macintosh / Apple Computer, Inc.Caldera Systems, SCO, SCO OpenServer, UnixWare / Caldera, Inc.TELEform / CardiffCheck Point, FireWall-1 / Check Point Software Technologies, Ltd.Unicenter / Computer Associates International, Inc.Access Logix, Celerra, Centera, CLARiiON, EMC, EMC2, MirrorView, Navisphere, SnapView, SRDF, Symmetrix, Symmetrix DMX,TimeFinder / EMC CorporationFujitsu / Fujitsu, Ltd.Hewlett-Packard, HP, HP-UX, HP Tru64, HP TruCluster, OpenVMS, ProLiant / Hewlett-Packard CompanyAIX, DB2, DB2 Universal Database, Domino, DYNIX, DYNIXptx, IBM, Informix, Lotus, Lotus Notes, OS/2, PTX, ptx/ADMIN, Raid Plus, ServeRAID, Sequent, Symmetry, Tivoli, / IBM CorporationInstallShield / InstallShield Software CorporationIntel, Itanium / Intel CorporationLinux / Linus TorvaldsActive Directory, Microsoft, MS-DOS, Outlook, SQL Server, Windows, Windows NT / Microsoft CorporationNetscape, Netscape Navigator / Netscape Communications CorporationData ONTAP, NetApp, NetCache, Network Appliance, SnapMirror, SnapRestore / Network Appliance, Inc.IntraNetWare, NetWare, Novell / Novell, Inc.Oracle, Oracle8i, Oracle9i / Oracle CorporationNetFORCE / Procom Technology, Inc.DLTtape / Quantum CorporationRed Hat / Red Hat, Inc.R/3, SAP / SAP AGIRIX, OpenVault, SGI / Silicon Graphics, Inc.SPARC / SPARC International, Inc.a

ACSLS, REELbackup, StorageTek / Storage Technology CorporationSolaris, Solstice Backup, Sun, SunOS, Sun StorEdge, Ultra / Sun Microsystems, Inc.SuSE / SuSE, Inc.Sybase / Sybase, Inc.Turbolinux / Turbolinux, Inc.Unicode / Unicode, Inc.VERITAS, VERITAS File System/ VERITAS Software CorporationWumpusWare / WumpusWare, LLCUNIX / X/Open Company Ltdb

Notes:

a. Products bearing SPARC trademarks are based on an architecture developed by Sun Microsystems, Inc.

b. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd.

All other brand or product names may be trademarks or registered trademarks of their respective owners.

LEGATO SoftwareA Division of EMC Corporation

End-User License AgreementTHIS PRODUCT CONTAINS CERTAIN COMPUTER PROGRAMS AND OTHER PROPRIETARY MATERIAL, THE USE OF WHICH IS SUBJECT TO THIS END-USER LICENSE AGREEMENT (THE "EULA"). DO NOT PROCEED WITH THE INSTALLATION OF THIS PRODUCT UNTIL YOU (LATER DEFINED AS LICENSEE) HAVE READ THIS EULA AND AGREE TO BE BOUND BY AND BECOME A PARTY TO THIS EULA. BY PROCEEDING WITH THE INSTALLATION OF THIS PRODUCT (OR AUTHORIZING ANY OTHER PERSON TO DO SO), YOU AND YOUR COMPANY ACCEPT THIS EULA AND YOU REPRESENT THAT YOU ARE AUTHORIZED TO DO SO. IF YOU ARE ACCESSING THE PRODUCT ELECTRONICALLY INDICATE YOUR ACCEPTANCE OF THESE TERMS BY SELECTING THE "ACCEPT" BUTTON AT THE END OF THE EULA. IF YOU DO NOT AGREE TO THE TERMS OF THIS EULA, YOU MAY RETURN THIS PRODUCT, ALL MEDIA AND DOCUMENTATION, AND PROOF OF PAYMENT, TO THE PLACE YOU OBTAINED THEM FOR A FULL REFUND WITHIN THIRTY (30) DAYS OF FIRST ACQUIRING THIS PRODUCT OR, IF THE PRODUCT IS ACCESSED ELECTRONICALLY, SELECT THE "DECLINE" BUTTON AT THE END OF THIS EULA AND RETURN PROOF OF PAYMENT IN ACCORDANCE WITH THE ABOVE REFERENCED RETURN/REFUND PROCESS. WRITTEN APPROVAL IS NOT A PREREQUISITE TO THE VALIDITY OR ENFORCEABILITY OF THIS EULA AND NO SOLICITATION OF ANY SUCH WRITTEN APPROVAL BY OR ON BEHALF OF LEGATO SHALL BE CONSTRUED AS AN INFERENCE TO THE CONTRARY. IF YOU HAVE ORDERED THIS PRODUCT, LEGATO'S ACCEPTANCE IS EXPRESSLY CONDITIONAL ON YOUR ASSENT TO THESE TERMS TO THE EXCLUSION OF ALL OTHER TERMS; IF THESE TERMS ARE CONSIDERED AN OFFER BY LEGATO, ACCEPTANCE IS EXPRESSLY LIMITED TO THESE TERMS.

1. DEFINITIONS

1.1 Authorization Code: means the unique code provided to Licensee by LEGATO for permanent activation of the Software. The Authorization Code is provided to Licensee once the Enabler Code is registered with LEGATO. The Authorization Code may be tied to a unique machine ID code supplied by Licensee.

1.2 Documentation: Documentation: means the user reference materials on any media, provided by LEGATO for use with the Software.

1.3 Enabler Code: means the code provided by LEGATO for activation of the Software.

1.4 Licensee: means the person or entity acquiring this License or for whom this License was acquired.

1.5 Software: means the object code copy of the software program provided to You in association with this EULA, together with the associated original media and all accompanying Documentation, and together with all Updates that may be provided by LEGATO to You from time to time.

2. OWNERSHIP AND ADMINISTRATION OF SOFTWARE

2.1 Ownership and Title. As between the parties, LEGATO, and its licensors, own and shall retain all right, title, and interest in and to: (i) the Software including all intellectual property rights embodied therein; (ii) all of the service marks, trademarks, trade names, or any other designations associated with the Software; and (iii) all copyrights, patent rights, trade secret rights, and other proprietary rights relating to the Software.

2.2 Software Activation. LEGATO employs Enabler Codes and Authorization Codes that enable the use of the Software. The Software is shipped in a ”Media Kit” which consists of object code software on CD-ROM and an Enabler Code for initial activation of the Software or the Software and Enabler Code may be delivered electronically. Once LEGATO receives confirmation from Licensee that the Software is installed with the correct Enabler Code, and is provided with the host ID information, LEGATO will provide the Authorization Code to Licensee. LEGATO administers the generation and distribution of Enabler and Authorization Codes, which administration may be modified by LEGATO from time to time.

2.3 Administration of Software. LEGATO may include on the media with the Software additional computer programs which are not currently licensed for use by Licensee and to which the Enabler Code or Authorization code will not permit access. Inclusion of such additional computer programs in no way implies a license from LEGATO and access or use of such programs is strictly prohibited unless Licensee procures the right to use any such program and the applicable Enabler Code is provided thereto.

3. LICENSE GRANT

3.1 Grant. LEGATO grants to Licensee a non-exclusive, nontransferable, non-sublicensable, perpetual (unless terminated in accordance with the provisions of this EULA), license (the “License”) to (i) use the Software installed in accordance with the Documentation and only on the licensed computer(s) solely for its own internal operations; and (ii) move the Software temporarily in case of computer system malfunction. The Software may be licensed: (a) on a per copy or per seat basis, on a physical or virtual machine, (b) based upon the number of mailboxes or the number of non-concurrent users for which it may be used, or (c) based upon data volumes it supports. The License granted under this EULA does not constitute a sale of the Software or any portion or copy of it. Licensee may not use the Software on more than one computer system unless otherwise specifically authorized by an explicit Software product, or additional licenses for additional computers are purchased. Rights not expressly granted are reserved by LEGATO.

3.2 Copies. Licensee may make copies of the Software provided that any such copy is: (i) created as an essential step in utilization of the Software as licensed and is used in no other manner; or (ii) used for archival purposes. All trademark and copyright notices must be reproduced and included on such copies. Licensee may not make any other copies of the Software.

3.3 Restrictions on use. Licensee shall not, and shall not aid, abet, or permit any third party to: (i) decompile, disassemble, or otherwise reverse engineer or attempt to reconstruct or discover any source code or underlying ideas or algorithms of the Software by any means whatsoever; (ii) remove any identification, copyright, or other notices from the Software; (iii) provide, lease, lend, use for timesharing or service bureau purposes; (iv) create a derivative work of any part of the Software; or (v) develop methods to enable unauthorized parties to use the Software. If EC law is applicable, the restrictions in Section 3.3 (i) are limited so that they prohibit such activity only to the maximum extent such activity may be prohibited without violating the EC Directive on the legal protection of computer programs. Notwithstanding the foregoing, prior to decompiling, disassembling, or otherwise reverse engineering any of the Software, Licensee shall request LEGATO in writing, to provide Licensee with such information or assistance and Licensee shall refrain from decompiling, disassembling, or otherwise reverse engineering any of the Software unless LEGATO cannot or has not complied with such request in a commercially reasonable amount of time.

3.4 Purchase Orders. Nothing contained in any purchase order, acknowledgment, or invoice shall in any way modify the terms or add any additional terms or conditions to this EULA.

3.5 Updates. This section applies if the Software acquired is an update to the original Software (the “Update”). An Update does not constitute a legally licensed copy of the Software unless purchased as an Update to a previously licensed version of the same Software. The Update may only be used in accordance with the provisions of this EULA. The Update, together with the original Software, constitutes one (1) legally licensed copy of the Software.

3.6 Evaluation License. This Section applies if the Software is being used for an initial thirty (30) day evaluation period. The license is valid only for a period of thirty (30) days from the delivery of the Software, and is designed to allow Licensee the right to evaluate the Software during such period. In the event that Licensee desires to continue to license the Software, Licensee must purchase a license to the Software. Upon such purchase, Licensee will be provided with an Enabler Code in accordance with Section 2.2 above. In the event Licensee determines not to purchase a license for the Software at the end of such thirty (30) day evaluation period, then Licensee’s rights under this EULA shall terminate automatically and Licensee shall promptly return to LEGATO or destroy all copies of the Software and so certify to LEGATO.

3.7 General Public License ("GPL"). The Software may include one or more components which are derived from software subject to a General Public License. Any such components are licensed exclusively under the applicable GPL and not under this EULA.

4. MAINTENANCE AND SUPPORT

4.1 LEGATO has no obligation to provide support, maintenance, upgrades, modifications, or new releases under this EULA. LEGATO may provide such services under separate EULA.

5. LIMITED WARRANTY

5.1 Media and Documentation. LEGATO warrants that if the media or documentation are damaged or physically defective at the time of delivery of the first copy of the Software to Licensee and if defective or damaged product is returned to LEGATO (postage prepaid) within thirty (30) days thereafter, then LEGATO will provide Licensee with replacements at no cost.

5.2 Limited Software Warranty. Subject to the conditions and limitations of liability stated herein, LEGATO warrants for a period of thirty (30) days from the delivery of the first copy of the Software to Licensee that the Software, as delivered, will materially conform to LEGATO’s then current published Documentation for the Software. This warranty covers only problems reported to LEGATO during the warranty period. For customers outside of the United States, this Limited Software Warranty shall be construed to limit the warranty to the minimum warranty required by law.

5.3 Remedies. The remedies available to Licensee hereunder for any such Software which does not perform as set out herein shall be either repair or replacement, or, if such remedy is not practicable in LEGATO’s opinion, refund of the license fees paid by Licensee upon a return of all copies of the Software to LEGATO. In the event of a refund this EULA shall terminate immediately without notice with respect to such Software.

6. WARRANTY DISCLAIMER

6.1 Warranty Disclaimer. EXCEPT FOR THE LIMITED WARRANTY PROVIDED IN SECTION 5 ABOVE, ALL SOFTWARE IS PROVIDED "AS IS". LEGATO AND ITS LICENSORS MAKE NO WARRANTIES WITH RESPECT TO ANY SOFTWARE AND DISCLAIMS ALL STATUTORY OR IMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR ARISING FROM A COURSE OF DEALING OR USAGE OF TRADE AND ANY WARRANTIES OF NONINFRINGEMENT. LEGATO DOES NOT WARRANT THAT THE SOFTWARE WILL MEET ANY REQUIREMENTS OR THAT THE OPERATION OF SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE. ANY LIABILITY OF LEGATO WITH RESPECT TO THE SOFTWARE OR THE PERFORMANCE THEREOF UNDER ANY WARRANTY, NEGLIGENCE, STRICT LIABILITY OR OTHER THEORY WILL BE LIMITED EXCLUSIVELY TO THE REMEDIES SPECIFIED IN SECTION 5.3 ABOVE. Some jurisdictions do not allow the exclusion of implied warranties or limitations on how long an implied warranty may last, so the above limitations may not be applicable.

7. LIMITATION OF LIABILITY

7.1 Limitation of Liability. EXCEPT FOR BODILY INJURY, LEGATO (AND ITS LICENSORS) WILL NOT BE LIABLE OR RESPONSIBLE WITH RESPECT TO THE SUBJECT MATTER OF THIS EULA UNDER ANY CONTRACT, NEGLIGENCE, STRICT LIABILITY, OR OTHER LEGAL OR EQUITABLE THEORY FOR: (I) ANY INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND WHETHER OR NOT ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH DAMAGES; OR (II) DAMAGES FOR LOST PROFITS OR LOST DATA; OR (III) COST OF PROCUREMENT OF SUBSTITUTE GOODS, TECHNOLOGY, SERVICES, OR RIGHTS; OR (IV) FOR AMOUNTS IN EXCESS OF THOSE RECEIVED BY LEGATO FOR THE PARTICULAR LEGATO SOFTWARE THAT CAUSED THE LIABILITY . Because some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, LEGATO's liability in such jurisdictions shall be limited to the extent permitted by law.

8. TERM AND TERMINATION

8.1 Term. The term of this EULA is perpetual unless terminated in accordance with its provisions.

8.2 Termination. LEGATO may terminate this EULA, without notice, upon Licensee's breach of any of the provisions hereof.

8.3 Effect of Termination. Upon termination of this EULA, Licensee agrees to cease all use of the Software and to return to LEGATO or destroy the Software and all Documentation and related materials in Licensee's possession, and so certify to LEGATO. Except for the License granted herein and as expressly provided herein, the terms of this EULA shall survive termination.

9. MISCELLANEOUS

9.1 Governing Law. This EULA shall be governed by the laws of the Commonwealth of Massachusetts, without regard to the principles of conflict of laws or the United Nations Convention on Contracts for the International Sale of Goods.

9.2 Government Restricted Rights. Any Software which is acquired directly or indirectly for or on behalf of the United States of America, its agencies and/or instrumentalities ("U.S. Government"), is provided with Restricted Rights. Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer Software - Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is LEGATO Software, a division of EMC Corporation, 2350 W. El Camino Real, Mountain View, CA 94040. The Software is a commercial software product, licensed on the open market at market prices, and was developed entirely at private expense and without the use of any government funds.

9.3 Export and Import Controls. Regardless of any disclosure made by Licensee to LEGATO of an ultimate destination of the Products, Licensee may not directly or indirectly export or transfer any portion of the Software, or any system containing a portion of the Software, to anyone outside the United States (including further export if Licensee took delivery outside the U.S.) without first complying with any export or import controls that may be imposed on the Software by the U.S. Government or any country or organization of nations within whose jurisdiction Licensee operates or does business. Licensee shall at all times strictly comply with all such laws, regulations, and orders, and agrees to commit no act which, directly or indirectly, would violate any such law, regulation or order.

9.4 Assignment. This EULA may not be assigned or transferred by Licensee without the prior written consent of LEGATO, which shall not be unreasonably withheld. LEGATO may assign or otherwise transfer any or all of its rights and obligations under this EULA upon notice to Licensee.

9.5 Sole Remedy and Allocation of Risk. Licensee's sole and exclusive remedies are set forth in this EULA. This EULA defines a mutually agreed-upon allocation of risk, and the License price reflects such allocation of risk.

9.6 Equitable Relief. The parties agree that a breach of this EULA adversely affecting LEGATO's intellectual property rights in the Software may cause irreparable injury to LEGATO for which monetary damages may not be an adequate remedy and LEGATO shall be entitled to equitable relief in addition to any remedies it may have hereunder or at law.

9.7 No Waiver. Failure by either party to enforce any provision of this EULA will not be deemed a waiver of future enforcement of that or any other provision, nor will any single or partial exercise of any right or power hereunder preclude further exercise of any other right hereunder.

9.8 Severability. If for any reason a court of competent jurisdiction finds any provision of this EULA, or portion thereof, to be unenforceable, that provision of the EULA will be enforced to the maximum extent permissible so as to effect the intent of the parties, and the remainder of this EULA will continue in full force and effect.

10. ENTIRE EULA

10.1 This EULA sets forth the entire understanding and EULA between the parties and may be amended only in a writing signed by authorized representatives of both parties. No vendor, distributor, reseller, dealer, retailer, sales person, or other person is authorized by LEGATO to modify this EULA or to make any warranty, representation, or promise which is different than, or in addition to, the warranties, representations, or promises made in this EULA. No pre-printed purchase order terms shall in any way modify, replace or supersede the terms of this EULA.

EmailXtender, Release 4.7 Release Notes 5

Contents

Preface....................................................................................................................... 9.

About This Document ..................................................................................................................... 9.

Information and Services................................................................................................................ 9.

Release Notes ......................................................................................................... 10.

New Features ............................................................................................................................... 10.

New Installation Process........................................................................................................ 11.

PST Migration Enhancements ............................................................................................... 11.

Legal Discovery Search Enhancements ................................................................................ 12.

HealthCheck Utility................................................................................................................. 12.

EmailXtract Enhancements.................................................................................................... 13.

Preview Pane Support for Shortcut Messages ...................................................................... 13.

OWA Shortcut Support Improvements................................................................................... 13.

Language Support Improvements.......................................................................................... 14.

Documentation Improvements ............................................................................................... 14.

Removed Features................................................................................................................. 14.

Installation and Update Notes ...................................................................................................... 15.

EmailXtender Server Upgrade Installation Does Not Recognize EmailXtender Server Components Installed on Remote Server .............................................................................. 15.

EmailXtract Log and Chart Directories Need to be Reset After Upgrading............................ 15.

exSearch.exe Task Must be Stopped Before Upgrading Search Plug-in .............................. 15.

Fixed Defects................................................................................................................................ 16.

Known Issues and Limitations ...................................................................................................... 19.

EmailXtract Non-Shortcut Issues ........................................................................................... 19.

User Can Delete EmailXtender Directory Files Using Delete Task ................................. 19.

EmailXtract Cannot Process Mailbox After Failover in a Domino Cluster ....................... 20.

EmailXtract Tasks Run as a Service Must Not Specify Mapped Network Drive as Log File Directory .......................................................................................................................... 20.

EmailXtract Does Not Archive Manually Copied Domino Messages............................... 20.

EmailXtract Cannot Archive Password Protected PST Files ........................................... 20.

EmailXtract Tasks Fail When Message Content Tab Contains Extended Characters .... 20.

Message Ownership Issues With Distribution Lists and the EmailXtract Archive Task... 21.

EmailXtender, Release 4.7 Release Notes

Contents

6

EmailXtract Shortcut Issues ................................................................................................... 21.

Shortcut Attachments Not Available if Notes 6.0 Database Has Soft Deletions Enabled 21.

Exchange Shortcuts Require that Registry Key Be Set Correctly ................................... 22.

Exchange 5.5 Shortcuts Do Not Function if LDAP Port is Not 389.................................. 22.

Exchange 5.5 or 2000 Shortcuts Created Before 4.7 Do Not Have Ownership Assigned After Upgrading to 4.7 ..................................................................................................... 22.

Cannot Create OWA Shortcuts in Folders with Names Containing \ or / Characters ...... 22.

Cannot Restore OWA Shortcuts in Folders with Names Containing # or % Characters . 22.

Restoring Shortcuts in Exchange 5.5 Public Folders May Not Remove Shortcut ........... 23.

Shortcutting Messages with Large Attachments Results in Error.................................... 23.

Access Denied Error When Creating OWA Shortcuts with Outlook 2003 ....................... 23.

Errors Generated Trying to Retrieve Shortcut Using OWA Against EmailXtender Server Running SSL ................................................................................................................... 23.

Issues Trying to Retrieve Shortcut Using Notes Against EmailXtender Server Running SSL24.

Search Issues ........................................................................................................................ 24.

Search Plug-in Results Exported to Container File for Users Removed From Address Book24.

Web Search From or Sent To Fields Should Not include Asterisk Character ................. 24.

Sun JRE Should Be Enabled as Java Plug-in for Netscape 7.1...................................... 24.

Wildcard Character Cannot Be Used to Match Space in Attachment Names ................. 24.

Stop Button Unresponsive When Performing Query ....................................................... 25.

Tasks Opened in Search Plug-In Are Copied to Current User's Task Folder.................. 25.

Cannot Search for Messages Sent to Distribution Lists Using Search Plug-in With Notes Client in Domino and Exchange Environment ................................................................. 25.

Cannot Query Mailboxes with Names Containing the @,=, or ;Characters..................... 25.

Certain Search Operators Do Not Function Properly ...................................................... 25.

Error Occurs When Copying to PST Folder From the Search Plug-in and PST Becomes Larger than 2 GB ............................................................................................................. 25.

Supervisor Search in Mixed-Mode Environment Returns No Results for Domino Mailboxes25.

Multiple Clients Exporting Search Results to PST/NSF Issues ....................................... 25.

Errors Generated When Accessing Notes Message Using Search Plug-In with Outlook on EmailXtender Server ....................................................................................................... 26.

EmailXtender Server Issues................................................................................................... 26.

EmailXtender Base with Administrator Setup Cannot Use Certain Characters in Database Name ............................................................................................................................... 26.

Exchange Message with .onm File Attachment is Archived But Not Indexed if EmailXtender is Not Configured for Exchange and Notes ..................................................................... 26.

Mail Rules Utilizing Action Rule in an SMTP Environment Fail ....................................... 26.


Contents

7

Notes Journaling Utility Starting and Stopping Feature Not Included on AS/400............ 26.

Journaling Disabled on All Domino Partition Servers When Only One Should Be Affected.26.

Journaling Initialization Messages From Partitioned Server Not Displayed on Domino Console ........................................................................................................................... 27.

Selecting Disable Archive in Folder Properties Can Result in Data Loss........................ 27.

Domain Inclusion and Exclusion Rule Issue When No Other Folders Present ............... 27.

EmailXtender Language Support Issues................................................................................ 27.

Messages Corrupted When Restoring Shortcuts in Exchange........................................ 27.

EmailXtract Task Failures Against Mailboxes with LATIN-2 Characters in Domino ........ 27.

EmailXtract Task Criteria Containing LATIN-1 or LATIN-2 Extended Characters Fail in Domino ............................................................................................................................ 27.

LATIN-1 and LATIN-2 Extended Characters in SMTP Messages Not Displayed/Searched28.

EmailXtract User Interface Character Display Issues...................................................... 28.

Search Results Page Not Displaying LATIN-1 and LATIN-2 Extended Characters Correctly28.

Similar EmailXtract MAPI Profiles Cause Conflicts on EmailXtender Server Issue......... 28.

EmailXaminer Interoperability Issues..................................................................................... 28.

EmailXaminer 2.1 Client and EmailXtender 4.7 Notes Search Plug-in are Incompatible When Installed on Same Computer................................................................................. 28.

Do Not Install Audit and EmailXaminer Manager on Same Computer ............................ 29.

EmailXtender Clients Should Not Be Installed on EmailXaminer Server......................... 29.

PST Migration Feature Can Impact EmailXaminer Performance .................................... 29.

Documentation Issues............................................................................................................ 31.

Missing Message Icon Blue Not Red............................................................................... 31.

Exporting Search Results to PST or NSF........................................................................ 31.

Enhanced EmailXtender Language Support ................................................................................ 31.

Support for German and French Language Environments .................................................... 31.

Selected Local Language Strings For Search Clients............................................................ 32.

Characters Supported in Messages and Attachments........................................................... 33.

LATIN-1 Character Support ............................................................................................. 33.

LATIN-2 Character Support ............................................................................................. 34.

Guidelines on Using EmailXtender with LATIN-1, LATIN-2, or MBCS Characters.......... 35.

System Requirements for LATIN-2 Support.............................................................. 35.

Using SMTP Messages with LATIN-1 or LATIN-2 Characters.................................. 36.

Using Messages with Multiple Languages and LATIN-2, MBCS or LMBCS Characters36.

Searching Messages Using Different Character Sets............................................... 36.


Contents

8

Displaying Messages Using Different Character Sets .............................................. 37.

Indexing LATIN-1 and LATIN-2 Messages Using a Single EmailXtender Server ..... 37.

Japanese and Simplified Chinese Language Support..................................................... 38.

System Requirements for Japanese or Simplified Chinese Support ........................ 38.

Processing Japanese or Simplified Chinese Multi-byte Messages........................... 39.

Processing Japanese or Simplified Chinese UTF-8 or UTF-7 Messages................. 40.

Documentation Additions.............................................................................................................. 40.

Conducting Wildcard Domain Address Searches on External Contacts................................ 40.

Assigning Owners to Messages Using EmailXtract ............................................................... 41.

Identity Management Guidelines for EmailXtender................................................................ 41.

What Is Identity Management? ........................................................................................ 41.

Managing Historical Address Information ........................................................................ 42.

Configuring Legacy Addresses for Existing Users........................................................... 42.

Configuring Legacy Addresses in Microsoft Exchange............................................. 43.

Configuring Legacy Addresses in Lotus Domino ...................................................... 43.

Conducting Effective Searches ....................................................................................... 43.

Documentation Improvements...................................................................................................... 44.

EmailXtender Installation Guide............................................................................................. 44.

EmailXtender Administrator’s Guide ...................................................................................... 45.

EmailXtender Search User’s Guide ....................................................................................... 46.

Online Help ............................................................................................................................ 46.

EmailXtender, Release 4.7Release Notes 9

Preface

Read the following Release Notes before installing the LEGATO EmailXtender® software.

About This DocumentThese Release Notes contain brief descriptions of new features, known limitations, configuration tips, and work arounds for this release of EmailXtender.

Late-breaking information obtained following the release of the CD-ROM is included in an electronic version of this document that is available in the Support section of the LEGATO web site, www.legato.com. Refer to the web site periodically to view the latest release of this document.

Information and ServicesLEGATO offers a variety of methods (including e-mail, telephone, and fax support) to obtain company, product, and technical information.

The LEGATO web site provides most of the information that customers might need, including technical bulletins and binary patches from its FTP site. For specific sales or training needs, e-mail or call LEGATO.

Service or ResourceTechnical Bulletins

Binary Patches

Company and Product Information Training

www.legato.com Yes Yes Yes Yes

LEGATO Sales(650) 210-7000 (option 1)[email protected]

Yes

LEGATO Education Services(650) [email protected]

Yes

http://www.legato.com


EmailXtender, Release 4.7Release Notes 10

Release Notes

This document provides information to supplement the EmailXtender, Release 4.7 documentation, which includes the EmailXtender Installation Guide, the EmailXtender Administrator’s Guide, and the EmailXtender Search User’s Guide. Use these guides in conjunction with these Release Notes.

This document covers the following topics:

• "New Features" on page 10• "Installation and Update Notes" on page 15• "Fixed Defects" on page 16• "Known Issues and Limitations" on page 19• "Enhanced EmailXtender Language Support" on page 31• "Documentation Additions" on page 40• "Documentation Improvements" on page 44

New FeaturesThe following new features have been added to EmailXtender in Release 4.7:

• "New Installation Process" on page 11• "PST Migration Enhancements" on page 11• "Legal Discovery Search Enhancements" on page 12• "HealthCheck Utility" on page 12• "EmailXtract Enhancements" on page 13• "Preview Pane Support for Shortcut Messages" on page 13• "OWA Shortcut Support Improvements" on page 13• "Language Support Improvements" on page 14• "Documentation Improvements" on page 14• "Removed Features" on page 14

EmailXtender, Release 4.7Release Notes

Release Notes

11

New Installation Process

The setup wizards for installing and updating EmailXtender components have been revised to simplify and streamline the installation process. You can now install multiple components at the same time.

A single server installation wizard allows you to install or update the following components on the EmailXtender server:

• EmailXtender server components• The EmailXtender Administrator interface• EmailXtender Audit• The Bloomberg Parser

• All EmailXtender documentation in .pdf format• The EmailXtender HealthCheck Utility• The EmailXtender Search Plug-in• EmailXtract

You can also use the server install to install EmailXtract on the mail server, or to install the EmailXtender Administrator interface or EmailXtender Audit on a client computer so that you can remotely administer EmailXtender and Audit.

A single client installation wizard allows you to install the EmailXtender Search Plug-in and the EmailXtender documentation in .pdf format on a client computer.

In addition, if you use "push" technology, such as Microsoft Systems Management Server (SMS), you can deploy a silent client installation across multiple computers simultaneously without having to run the installation at each computer.

For more information on the new installation process, refer to the EmailXtender Installation Guide.

PST Migration Enhancements

Microsoft Exchange .pst files located on client computers or in other locations can represent challenges for companies that want to be able to ensure that all items associated with Microsoft Outlook users are archived in EmailXtender. Enhancements in Release 4.7 make the process for selecting and managing .pst files for migration more flexible and robust. Using EmailXtract, you can now:

• Find and select .pst files – You can automatically find or manually browse the network for .pst files. Once .pst files are discovered, you can select the ones you want to process.

• Determine .pst ownership (automatically or manually) – When you select one or more .pst files, EmailXtract attempts to automatically determine the owner of the .pst file using addressing information in the file. In cases where ownership cannot be automatically determined, you can manually associate an owner with the .pst file.

• Create shortcuts to archived items in the end user’s Outlook client interface – Once the migration is completed, you can use the Shortcut to Mailbox option to create a new folder in the owner’s mailbox on the Microsoft Exchange server (identified by the .pst file name), which preserves the .pst folder structure and shortcuts to each message. This allows the end user access to the messages while


Release Notes

12

eliminating the need for a .pst file to exist on the end user’s local machine. Alternatively, you can create shortcuts to the messages in the .pst file on the end user’s local machine.

• Delete, move, hide, or make .pst files read-only after they have been archived – You can then perform post-processing actions on the .pst files which include deleting, hiding, moving or marking them as read-only. This enables you to eliminate the need for .pst files to exist on an end user’s local machine.

For more information, refer to the EmailXtract chapter of the EmailXtender Administrator’s Guide.

Legal Discovery Search Enhancements

EmailXtender search capabilities have been enhanced to make searches easier and more productive, especially for legal discovery searches. These enhancements include the ability to:

• Use a single search query to find all messages for a particular user• Export search results into .pst or .nsf files• Search for all messages sent between specific users and domains• Search for all email messages sent to domain names with wildcard support, for

example, *@emc.com• Perform an unattended search and export the results without further user

interaction, logging any errors in a log file• Automatically place search results into multiple .pst or .nsf files based on a

specified maximum size

For more information on using these new search capabilities, refer to the EmailXtender Search User’s Guide.

HealthCheck Utility

The new HealthCheck utility allows you to maintain the data on a local or remote EmailXtender server using a graphical user interface. Using the HealthCheck utility, you can perform the following maintenance tasks:

• Verify that all messages were archived for each month, index, and volume• Verify that messages are not missing from a volume• Rebuild a corrupt month or index

For example, you may determine from the EmailXtender Administrator interface that a volume is missing a message because the status icon for the volume changes.You can then use the HealthCheck utility to verify whether the message appears in the EmailXtender database, and then either re-index the volume or delete the identifier for the message from the database.

For more information on using the HealthCheck Utility, refer to the Maintenance chapter of the EmailXtender Administrator’s Guide.


Release Notes

13

EmailXtract Enhancements

EmailXtract has added several new features in addition to the .pst migration enhancements:

• Automatic assignment of message ownership -- EmailXtract now dynamically assigns message ownership information to blind carbon copy (BCC) messages and messages sent to distribution lists. This allows EmailXtract to update message ownership information over time.– Messages sent to distribution lists -- When a message is sent to a distribution

list, EmailXtract finds the message in the user's mailbox and archives it, assigning the user and the distribution list as owners of the message. When EmailXtract subsequently finds the same message in another user's mailbox, it recognizes the message as a duplicate and assigns the second user as an additional owner of the message.

– Messages sent to BCC addresses -- When a message includes users and distribution lists in the BCC field, EmailXtract finds the message in the user's mailbox and archives it, assigning the user as the owner of the message. When EmailXtract subsequently finds the same message in a BCC recipient’s mailbox, it recognizes the message as a duplicate and assigns the BCC recipients as additional owners of the message.

• EmailXtract tasks run as a service -- This means that the user account does not have to be logged on for such tasks to run.

• Mixed mail support -- If you are using both Lotus Domino and Microsoft Exchange, you can now install and use EmailXtract on the same computer with both environments.

• Verifying shortcuts -- You can now identify and remove shortcuts that are no longer valid more easily when you run a Shortcut task using the Verify Shortcuts option on the Shortcut tab.

For more information on these new EmailXtract features, refer to the EmailXtract chapter of the EmailXtender Administrator’s Guide.

Preview Pane Support for Shortcut Messages

Microsoft Outlook users can now view shortcut messages using the Outlook preview pane without restoring the messages. To enable preview pane support, you must install a COM Add-in on the client computers. If you install or update the Search Plug-in on client computers, the COM Add-in is installed automatically. If you do not want to install or update the Search Plug-in, you can install only the COM Add-in. For more information, refer to the EmailXtender Installation Guide.

OWA Shortcut Support Improvements

Significant improvements have been made in EmailXtender’s support for viewing shortcuts using Microsoft Outlook Web Access (OWA), including support for the following:

• Using forms authentication• Using shortcuts over HTTPS/SSL


Release Notes

14

• User-defined port assignment for resolving shortcuts• Using OWA in a Microsoft Cluster Server environment

For more information on installing shortcut support for OWA, refer to the Microsoft Exchange Journaling and Shortcut Support chapter of the EmailXtender Installation Guide.

Language Support Improvements

EmailXtender supports the processing of messages and attachments in a variety of languages. This support now includes the use of EmailXender on German and French versions of Windows, providing selected local language strings for the Search Plug-in and the Web Search client, and processing messages and attachments in LATIN-1, LATIN-2, Japanese and Simplified Chinese languages.

For more information, see "Enhanced EmailXtender Language Support" on page 31.

Documentation Improvements

The EmailXtender documentation suite was reorganized to be more task-based and user-friendly. In addition, additional best practices information has been added on several subjects, including how to:

• Regularly maintain an EmailXtender server• Troubleshoot problems in the EmailXtender environment• Configure antivirus software with EmailXtender• Install and configure DiskXtender for use in an EmailXtender environment

For more information on the documentation changes in EmailXtender, Release 4.7, see "Documentation Improvements" on page 44.

Removed Features

The following features, which appeared in earlier releases of EmailXtender, have been removed in Release 4.7:

• Direct support of CD-R devices -- To archive container files to removable storage media, use LEGATO DiskXtender 2000. For more information on using DiskXtender with EmailXtender, refer to the Configuring Message Archival chapter of the EmailXtender Administrator’s Guide.

• Selective indexing of attachments -- You can no longer exclude certain types of attachment file types from being indexed using the Attachments tab of the Cabinet Properties dialog box; EmailXtender indexes all supported attachment types automatically.

• Indexing statistics -- You can no longer view indexing statistics using the Statistics tab of the Cabinet Properties dialog box.

• Prepend "(Archived)" to message subject option -- You can no longer use this option to modify the subject of Notes messages using EmailXtract.


Release Notes

15

Installation and Update NotesThe software for installing and updating EmailXtender components have been revised to simplify and streamline the installation process. Because the installation process has changed significantly, you should review the installation information provided in the EmailXtender Installation Guide before you install or update EmailXtender and its components.

Patches and updates to EmailXtender are published on the EmailXtender FTP site (ftp://ftp.legato.com/pub/EmailXtender). You should check this site after you install EmailXtender to ensure you have the latest patch.

Prior to installing a patch or update from the FTP site, review the ReadMe.txt file in the /EmailXtender directory and the EXReleasePatch.htm file (where Release is the EmailXtender release number and Patch is the patch number) in the directory for the patch or update that you plan to install.

If you are not certain whether a patch is appropriate for your installation, or if you need assistance in applying the patch or update, contact technical support for assistance.

The following sections describe known issues with the installation process.

EmailXtender Server Upgrade Installation Does Not Recognize EmailXtender Server Components Installed on Remote Server

When the EmailXtender Server installation is used to perform an upgrade, the installation does not recognize components installed on a remote computer, such as the EmailXtender Administrator, EmailXtender Audit, or EmailXtract. The upgrade procedure will recognize and upgrade the Search Plug-in on a remote computer.

To work around this problem, uninstall the components on the remote computer and then re-install those components using the EmailXtender 4.7 installation. (SDR 11928)

EmailXtract Log and Chart Directories Need to be Reset After Upgrading

Before upgrading EmailXtender Server 4.7, backup any EmailXtract log files that you wish to save; these files will be deleted by the upgrade.

Once the upgrade is complete, any EmailXtract tasks that create logs or charts will need to have the directories for those logs or charts reset. You set the directories for logs or charts by selecting Configuration Properties from the Options menu in EmailXtract. On the displayed Configuration Options window, enter the new directories in the Log Files and the Chart Files areas. (SDR 12160)

exSearch.exe Task Must be Stopped Before Upgrading Search Plug-in

Before upgrading the Search Plug-in, the process exSearch.exe must be stopped. If it is not stopped the following message is displayed:

Search Plug In needs to be shut down before installation can continue"

This is also true for SMS upgrades of the Search Plug-in. (SDR 12148)


Release Notes

16

Fixed DefectsThe following table lists the defects corrected in EmailXtender 4.7 by software defect report (SDR) number.

Table 1. Summary of Corrected Defects

SDR Fix Description

12071 Fixed problem with restoration of shortcut messages.

11969 Fixed semaphore lock error causing Domino server crash.

11800 Archiving messages through EmailXtract resulted in "Error Processing Recipients" when parent folder contained MBCS messages.

11793 Fixed slow performance experienced when running a User Search.

11768 No longer any problems using the EXNotesMgr.exe process.

11731 Notes Databases are now created with correct default of transactional logging disabled.

11730 Domino installer could not install on a multi-partioned Domino server.

11679 Journaling problems with Domino messages on IBM AIX have been corrected.

11675 Restoring shortcuts from a Domino server does not take a long period of time.

11612 Fix for Domino 6.5.2 listener on RedHat Linux resolved $Reader data problem.

11450 Messages no longer cause the Unable to load Compound Message error when copying to a folder.

11443 Messages are no longer duplicated when using multiple Domino servers.

11436 EmailXtender processes messages correctly when Norton Anti-virus software does not interact with EmailXtender directory.

11435 Updating servers to current patch level resolves error reporting problem.

11433 Delivered AS/400 version of shortcut library for Domino server.

11397 Setting a flag in the Volume Restore queue prevents volumes from being deleted after a restore process, allowing migrated volumes to remain intact.

11370 Customer-specific code change resolves EmailXaminer posting messages to wrong sample set by allowing EmailXtender to populate the EmailXaminer queue with the date received by EmailXtender and not the current date.

11368 Application of new binaries resolves index service hanging.


Release Notes

17

11349 Messages can be copied to a folder from the Search Plug-in with the French locale set.

11333 User having a valid email address but an ambiguous display name is now validated correctly using EmailXtract.

11278 External SMTP messages with BCC addressing are processed correctly.

11275 Documents are not erroneously deleted when shortcuts are restored.

11271 EmailXtract shortcut functionality with Notes acceptable.

11215 Using different method to determine Outlook client version installed resolved problem with creating shortcuts.

11196 Restoring shortcuts no longer cause the Domino server to crash.

11158 Rebuilding EmailXtender server resolves exception in exexchangemailbox.exe.

11145 Reload of Exchange Server 2000 SP3 corrects reported failure.

11119 EmailXtract properly processes messages when the selected date range is something other than "All Dates."

11039 Allowed service account names to contain a period.

11034 Messages prefixed with a comma are pulled from the journal mailbox.

11031 The Admin service no longer crashes when Activate Changes is selected when there are a large number of volumes to process.

10988 MIME information is not lost after archiving with EmailXtract.

10973 Enabled flag to allow a shortcut to be made to the email without modifying the Notes time stamp. Domino server now remains stable during server replications of shortcut mail database to a Notes client.

10962 Installing the Notes search client on a mapped network drive no longer causes authentication problems with the EmailXtender server.

10958 Using DNS alias to selected server on a WAN allows DLC build to occur in normal timeframe.

10956 Notes attachment properties now show correct time.

10931 Messages can be copied from the Search Plug-in when using German/Swiss Regional Settings.

10902 Enabled shortcuts to be updated without modifying the Notes time stamp. Domino server now remains stable during shortcut retrieval by Out of Office agent.


SDR Fix Description


Release Notes

18

10763 Changes to memory management enable large query searches.

10741 11208

Problems with services hanging have been fixed.

10736 SMTP Messages no longer fail to unpack.

10590 Microsoft Office summary information is now being indexed for all Microsoft Office documents.

10355 User is now requested to restart indexing, which resolves unintended indexing of attachments.

10347 The Search Plug-in for Notes works correctly when the Notes client is set to Island mode.

10340 Upgrading EmailXtender resolves client authentication failure.

10307 Provided EXProcBaddocs library for Red Hat Linux AS 2.1.

10305 Provided ExProcBaddocs library for IBM AIX 5.1.

10290 Fixed exjournal.ntf and exshortcut.ntf to have unique replica identifiers.

1025710739

EmailXtract processes messages with large attachments correctly.

10244 The EmailXtender .dlc file is created appropriately.

10230 Provided information on the necessary permissions for journaling with EmailXtender and Exchange.

10226 Translating native text to LMBCS prior to setting the text in the Notes item retains German language characters.

10202 Shortcuts now perform correctly when using Outlook 2003 with cached mode enabled.

10139 "Matching Hits" is now correctly translated when using German Search Plug-in.

10087 Fixed a scripting error that caused certain messages from the Domino server to get stuck in message queues. Messages now being pulled from the Notes server correctly.

10013 Messages no longer are stuck in the exjournal.nsf file.

09887 Problems using shortcuts with Outlook Web Access (OWA) have been resolved.

09882 Problematic messages that were placed in the Baddir directory are now successfully processed by later version of EmailXtender.


SDR Fix Description


Release Notes

19

Known Issues and LimitationsThe following sections list the known issues and limitations in EmailXtender, Release 4.7:

• "EmailXtract Non-Shortcut Issues" on page 19• "EmailXtract Shortcut Issues" on page 21• "Search Issues" on page 24• "EmailXtender Server Issues" on page 26• "EmailXtender Language Support Issues" on page 27• "EmailXaminer Interoperability Issues" on page 28• "Documentation Issues" on page 31

EmailXtract Non-Shortcut Issues

The following are known issues in using EmailXtract that do not deal with shortcuts.

User Can Delete EmailXtender Directory Files Using Delete Task

If an EmailXtract Delete task is run on the root of the Exchange Public Folders, and OWA support is installed for Exchange, then files in the EmailXtender directory are deleted. You should not use the Delete task in this way. (SDR 4465)

09802 The Admin service no longer crashes when adding a mailbox.

09395 When opening shortcut messages with a Subject line containing a slash followed by non-English characters, changed a method to now convert the URL to the UTF-8 standard and then escape the illegal URL characters with their ASCII counterparts.

09266 Could not verify OWA user account during install unless the user was in the Default Users container in Active Directory.

09220 OWA now properly authenticates users.

08626 Upgrade to Domino servers resolves problem with ExAddRule.

08615 EmailXtender works with Domino 6.5.1 installed on an AIX dual processor system.

08079 The Address Rule Service no longer crashes.

06356 Enabled Notes to pull messages with attachments from a journaling mailbox on EmailXtender if the attachment size is not the same as what Notes recorded.


SDR Fix Description


Release Notes

20

EmailXtract Cannot Process Mailbox After Failover in a Domino Cluster

In the Domino cluster environment, EmailXtract cannot process Domino messages after the Domino server fails over to another server in the cluster. EmailXtract does not recognize the new server, and continues to attempt to access the original server.

The error message returned is:

Mailbox: NA2_User1/CME - mail\na2user1.nsf*** NOTES Error in mailbox NA2_User1: Remote system not responding

(SDR 11694)

EmailXtract Tasks Run as a Service Must Not Specify Mapped Network Drive as Log File Directory

When creating EmailXtract tasks that are to be run as a service, the path to the log file directory cannot include a mapped network drive letter. To specify a network location, specify the complete network path instead of using a mapped network drive letter. For example, specifying Y:\MyData\EmailXtenderLogs\ would not function properly, but specifying \\remotecomputer\MyData\EmailXtenderLogs\ would function properly.

You specify the log file location on the Directories tab of the Configuration Options dialog box. (SDR 11587)

EmailXtract Does Not Archive Manually Copied Domino Messages

When a Domino message is manually copied into a mailbox, and the EmailXtract Archive task is run on that mailbox, the message copied into the mailbox is not archived because the message’s modified date is earlier than the archive date on the mailbox. This problem does not occur with Exchange messages. (SDR 11734)

EmailXtract Cannot Archive Password Protected PST Files

To use EmailXtract to archive password protected PST files, open the PST file in Outlook, remove the password, and then use EmailXtract to archive the file. (SDR 30046)

EmailXtract Tasks Fail When Message Content Tab Contains Extended Characters

If an EmailXtract Archive, Shortcut, or Delete task is run that contains a LATIN-1 or LATIN-2 extended character (those characters with values greater than 128) in the Subject, Attachments, From or Sent to fields of the Message Content tab, that task will fail, but no data loss or crash will occur. (SDR 12243)


Release Notes

21

Message Ownership Issues With Distribution Lists and the EmailXtract Archive Task

Message ownership issues may be experienced when all of the following situations occur:

1. A message is sent to a distribution list and journaled by EmailXtender 4.7.

2. The same message is subsequently moved to another user’s mailbox who was not a member of the distribution list associated with the original message.

3. The EmailXtract Archive task is subsequently run against this user’s mailbox.

When a message sent to a distribution list is journaled, the distribution list is expanded, and all members in the list are associated as owners of the message. When a message sent to a distribution list is archived using EmailXtract, the distribution list is not expanded (since distribution lists can change over time). Therefore, the distribution list name is associated with the To: field. When the EmailXtract task is run, the message ownership is now attributed to the distribution list name. Searching the To: field for original members of the distribution list will not return the message.

A patch containing a resolution to this issue will be released shortly. To correct this problem, you can do one of the following:

• Perform a search using the Mailbox field instead of the To: field.• Re-index the volume in which the message is stored. (SDR 12266)

EmailXtract Shortcut Issues

The following are known issues in using EmailXtract that deal with shortcuts.

Shortcut Attachments Not Available if Notes 6.0 Database Has Soft Deletions Enabled

If soft deletions are enabled on the Lotus Domino 6.0 database being archived by EmailXtender, messages that have been shortcut will not be able to retrieve their associated attachments. This problem only occurs with Lotus Domino versions 6.0.1, 6.0.2, and 6.0.3. It does not occur with Lotus Domino 6.5 or higher.

To correct this problem, disable soft deletions on the database.

To disable soft deletions on one or more databases using the Notes Administrator client, the user account must have manager access to the one or more databases through ACLs. To disable soft deletions, do the following:

1. Launch the Domino Administrator.

2. Select the tab for the mail server to be changed.

3. Select the Files tab. On this tab, expand the data directory tree and select the mail folder. The mail databases that exist in that folder are displayed.

4. Select the one or more databases to change. Right-click one of the selected databases and select Advanced Properties. The Advanced Database Properties window is displayed.


Release Notes

22

5. On the Advanced Database Properties window, select the database property to modify for all the selected databases by clicking the check box in the Select column that is next to the Allow soft deletions option. A second check box is then activated. Verify that the second check box is unchecked to indicate that soft deletions are not allowed. If the second check box is checked, click it to clear the check mark.

6. Click OK.

(SDR 6911)

Exchange Shortcuts Require that Registry Key Be Set Correctly

Exchange shortcuts cannot be resolved when the LoadBehavior registry key used by the Outlook mail client has the wrong value.

The following registry key needs to be set to a value of 3:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins\ExOutlookAddin.ShortcutAddin\LoadBehavior

(SDR 12188)

Exchange 5.5 Shortcuts Do Not Function if LDAP Port is Not 389

Exchange 5.5 shortcuts do not function if the LDAP port number is set to something other than the default value of 389. (SDR 12166)

Exchange 5.5 or 2000 Shortcuts Created Before 4.7 Do Not Have Ownership Assigned After Upgrading to 4.7

After upgrading to EmailXtender 4.7, Exchange 5.5 or Exchange 2000 shortcuts created with previous versions of EmailXtender will not have their message ownership evaluated when they are archived using EmailXtract because of problems with BCC recipients.

To work around this problem for Exchange 2000, apply the fix described in Microsoft Knowledge Base article 810999, http://support.microsoft.com/kb/810999. There is no work around for Exchange 5.5. (SDR 11926)

Cannot Create OWA Shortcuts in Folders with Names Containing \ or / Characters

EmailXtract cannot create Outlook Web Access (OWA) shortcuts in folders with names containing the \ or / characters. (SDR 37371)

Cannot Restore OWA Shortcuts in Folders with Names Containing # or % Characters

EmailXtract cannot restore OWA shortcuts to folders with names containing the # or % characters, and will return the following message:

Failed to open shortcut. Could not rebuild the original message. Error code: 0x80004005. Error description: Unknown Error

(SDR 37558 and SDR 37560)


Release Notes

23

Restoring Shortcuts in Exchange 5.5 Public Folders May Not Remove Shortcut

When restoring a shortcut located in Exchange 5.5 public folders, the message will be restored but the shortcut will remain. To resolve this issue, edit the public folder permissions and change the default user to have either editor or owner permissions. You can also resolve the issue by adding the EmailXtender server user account as editor or owner. (SDR 34987)

Shortcutting Messages with Large Attachments Results in Error

When using the Shortcut task in EmailXtract to shortcut a message with a large attachment (such as a 100 MB attachment), EmailXtract does not shortcut the message and returns the following error:

Unknown error during Xtraction Task

This prevents the message from being shortcutted. (SDR 10257)

Access Denied Error When Creating OWA Shortcuts with Outlook 2003

When creating a shortcut with the OWA option enabled with Exchange 2003, the Connect To login dialog box may appear. If you click Cancel to exit the dialog box, the following error appears in EmailXtract:

Access denied for GetstatusText in SetOWA2KProps

This problem is caused by the more restrictive security settings in Windows 2003. Windows 2003 is installed with the Internet Explorer Enhanced Security Configuration option enabled which prevents access to local intranet sites unless those sites are specifically granted permissions.

If the Internet Explorer Enhanced Security Configuration option is disabled for administrator groups, EmailXtract does not display the Connect To login, and the error does not occur. To disable the Internet Explorer Enhanced Security Configuration option, do the following:

1. From the Start menu, click Settings>Control Panel>Add or Remove Programs.

2. In the Add or Remove Programs dialog, click Add/Remove Windows Components.

3. In the Add/Remove Windows Components dialog, unselect the Internet Explorer Enhanced Security Configuration option.

(SDR 8175, 39423)

Errors Generated Trying to Retrieve Shortcut Using OWA Against EmailXtender Server Running SSL

If the EmailXtender server has been configured to only allow SSL connections, errors are generated when trying to retrieve shortcuts using Outlook Web Access. To resolve this issue, modify the custom attribute of the EmailXtender contact from:

http:// <EmailXtender Server>/Exshortcut/query.asp

to the following:

https:// <EmailXtender Server>/Exshortcut/query.asp. (SDR 12286)


Release Notes

24

Issues Trying to Retrieve Shortcut Using Notes Against EmailXtender Server Running SSL

If the EmailXtender server has been configured to only allow SSL connections, shortcuts cannot be retrieved using Notes using the Shortcut Extension Manager installed on the Domino server. Shortcuts can be retrieved by opening the .NEX file which appears when a shortcut is accessed. To retrieve shortcuts using the .NEX file, the EmailXtender Search Plug-In must be installed and configured on the Notes client. (SDR 12284)

Search Issues

The following are known issues in using search.

Search Plug-in Results Exported to Container File for Users Removed From Address Book

If you configure the Search Plug-in to export search results to a .pst or .nsf file, and you configure the container file options and enable the Separate messages by Owner option, some messages cannot be separated by owner. This situation occurs when a search is conducted which returns messages sent to a distribution list which includes a user who has been removed from the address book and removed as a member of a distribution list. When such messages are found, the user cannot be associated as the owner of these messages during the export to container file. These messages are placed in a container file named Unknown.pst or Unknown.nsf. (SDR 11775)

Web Search From or Sent To Fields Should Not include Asterisk Character

When searching using the Web search client, you cannot specify an asterisk character (*) as part of the From or the Sent To fields. You can use this character as a wildcard character with the Search Plug-in if you follow the rules described in the Entering Addresses Using Wildcards section of the EmailXtender Search User’s Guide. (SDR 10652)

Sun JRE Should Be Enabled as Java Plug-in for Netscape 7.1

When using the Web Search client from a Netscape 7.1 browser, the display may be difficult to read. To correct this problem, make sure that the Sun Java Run-time Environment (JRE), is enabled to be the Java plug-in for Netscape 7.1. (SDR 10530)

Wildcard Character Cannot Be Used to Match Space in Attachment Names

When performing a search for an attachment using the Web client or the Search plug-in, an asterisk cannot be used to match a space in the name of an attachment. For example, when searching for an attachment named Phone Numbers.txt, the query Phone*Numbers.txt would not match that name. However, the query Phone Number*.txt would match the name. (SDR 10983)


Release Notes

25

Stop Button Unresponsive When Performing Query

The Search Plug-in will continue to perform the current query until it finishes processing the current index, regardless of whether the Stop button is used. Completing the processing of the current index may take a few minutes. (SDR 36296)

Tasks Opened in Search Plug-In Are Copied to Current User's Task Folder

When searching and viewing tasks that are the result of queries in the Search Plug-in for Outlook, those tasks are copied into the current user’s Task folder. (SDR 31873)

Cannot Search for Messages Sent to Distribution Lists Using Search Plug-in With Notes Client in Domino and Exchange Environment

The Notes Search Plug-in cannot search for distribution lists if you are archiving messages from both Exchange and Lotus Notes. (SDR 37194)

Cannot Query Mailboxes with Names Containing the @,=, or ;Characters

Performing queries on mailboxes with names containing the at sign (@), equals sign (=) or semicolon (;) character will not return any results. (SDRs 36236, 36237, and 36238)

Certain Search Operators Do Not Function Properly

There are certain operators that do not perform as intended or documented. They consist of the following: XVSIZE, IN, and LABEL. (SDRs 37017, 37011)

Error Occurs When Copying to PST Folder From the Search Plug-in and PST Becomes Larger than 2 GB

A Reason 0 error occurs when copying messages to a PST folder using the Search Plug-in and the size of the PST file becomes greater than 2 GB. (SDR 8655, 40553)

Supervisor Search in Mixed-Mode Environment Returns No Results for Domino Mailboxes

In a mixed-mode environment (Lotus Domino and Microsoft Exchange) only. If a Supervisor Search is conducted by a Domino user against a Domino mailbox using the Search Plug-in or the Web Search client, no results are returned. (SDR 12273)

Multiple Clients Exporting Search Results to PST/NSF Issues

If you have two or more instances of the Search Plug-in running on the same machine and are simultaneously exporting search results to PST or NSF files, indications that the export has completed may not appear, although the exports are successfully completed. Also, when exporting results to PST or NSF files, the resulting files are placed in a dynamically-generated sub-directory within the output directory specified in the export settings. (SDR 12108)


Release Notes

26

Errors Generated When Accessing Notes Message Using Search Plug-In with Outlook on EmailXtender Server

If EmailXtender has been installed to support both Domino and Exchange environments, errors are generated when trying to access Notes messages using the Search Plug-In with the Outlook mail client. This issue only occurs on the EmailXtender server. Clients which have the Search Plug-In installed for both Notes and Outlook do not have this issue. (SDR 10264, 122920)

EmailXtender Server Issues

The following are known issues in using the EmailXtender server.

EmailXtender Base with Administrator Setup Cannot Use Certain Characters in Database Name

The following characters cannot be used in the name of the SQL database being created for EmailXtender:

~`!@#$%^&()-+={[}];'<,>.

(SDR 35789)

Exchange Message with .onm File Attachment is Archived But Not Indexed if EmailXtender is Not Configured for Exchange and Notes

Messages that have .onm files (EmailXtender Notes messages) are archived but the contents of the .onm files are not indexed, unless EmailXtender is installed with both Notes and Exchange support. (SDR 35841)

Mail Rules Utilizing Action Rule in an SMTP Environment Fail

When an Action mail rule is set for an SMTP environment, no messages are forwarded as intended. (SDR 37051, 7248)

Notes Journaling Utility Starting and Stopping Feature Not Included on AS/400

The EmailXtender Lotus Notes Journaling Utility starting and stopping feature is not supported on a Domino server installed on an AS/400 computer. (SDR 38017)

Journaling Disabled on All Domino Partition Servers When Only One Should Be Affected

When EmailXtender journaling is disabled on one partition of a Domino partition server, all the Domino servers on that computer will have journaling disabled instead of just the selected Domino server. (SDR 12088)


Release Notes

27

Journaling Initialization Messages From Partitioned Server Not Displayed on Domino Console

When EmailXtender journaling is started with two or more Domino partitioned servers on a computer, the messages indicating journaling is starting are only displayed at the console for the first server journaled, initialization messages for the journaling of the other servers are not displayed at the console. However, those message are available in the \Data\log.nsf file for each server. (SDR 12092)

Selecting Disable Archive in Folder Properties Can Result in Data Loss

If you have only one folder defined within a cabinet, do not select the Disable Archive option on the Folder Properties dialog box, or you could experience loss of data. (SDR 12277)

Domain Inclusion and Exclusion Rule Issue When No Other Folders Present

Domain inclusion and exclusion rules do not function properly when no other folders are present into which mail can be archived. This causes mail to not be archived in the folder with the domain rule.

To resolve this issue, add another folder with a keyword inclusion rule in which the keyword is a random string that is not likely to be matched (for example, $#$#$#). This enables mail to be pulled from the mail server, and mail that matches the domain rule will be archived in the folder with the domain rule. A patch containing a resolution to this issue will be released shortly. (SDR 12177)

EmailXtender Language Support Issues

The following are known issues with EmailXtender language support.

Messages Corrupted When Restoring Shortcuts in Exchange

For Microsoft Exchange Environments only. When messages with LATIN-2 extended characters are shortcutted using EmailXtract, and then restored to the mail server by opening in Outlook, the message subject and display name appear corrupted. (SDR 12195)

EmailXtract Task Failures Against Mailboxes with LATIN-2 Characters in Domino

For Lotus Domino environments only. EmailXtract tasks fail when run against a mailbox created in Lotus Domino with LATIN-2 extended characters. (SDR 12264)

EmailXtract Task Criteria Containing LATIN-1 or LATIN-2 Extended Characters Fail in Domino

For Lotus Domino environments only. If you specify task criteria using LATIN-1 or LATIN-2 extended characters in the Message Content or Mailbox Selection tabs used to define a task in EmailXtract, the task fails. (SDR 12243, 12213)


Release Notes

28

LATIN-1 and LATIN-2 Extended Characters in SMTP Messages Not Displayed/Searched

LATIN-1 and LATIN-2 extended characters in the subject, body or attachment filename of an SMTP message cannot be correctly displayed, indexed or searched. (SDR 11920, 11850)

EmailXtract User Interface Character Display Issues

The EmailXtract user interface details window and log files cannot display some LATIN-1 and LATIN-2 characters. (SDR 12076)

Search Results Page Not Displaying LATIN-1 and LATIN-2 Extended Characters Correctly

LATIN-1 and LATIN-2 extended characters (ranging from 129-159) are not displayed correctly in the search results page when using the Search Plug-in. However, when you open a message from the results page, the characters are displayed correctly. (SDR 12294)

Similar EmailXtract MAPI Profiles Cause Conflicts on EmailXtender Server Issue

For Microsoft Exchange environments only. An issue occurs when an Outlook profile with a name similar to the EmailXtract MAPI profile exists on the EmailXtender server (for example, Admin1 and Admin2). When you perform an EmailXtract task for mixed-language messages (e.g, a mail environment where English, Polish, or Japanese messages are processed), the ambiguous MAPI profiles may conflict and generate Profile code page errors. To resolve this issue, ensure that the names of any MAPI profiles on the EmailXtender server are unique. (SDR 12218)

EmailXaminer Interoperability Issues

The following are known issues in using EmailXtender with EmailXaminer.

EmailXaminer 2.1 Client and EmailXtender 4.7 Notes Search Plug-in are Incompatible When Installed on Same Computer

Files installed by the EmailXtender 4.7 Notes Search Plug-in are more current that those installed by the EmailXaminer 2.1 client, and are incompatible with the older versions. This causes the EmailXaminer 2.1 client to not function properly.

To work around the incompatibility issues, do one of the following, based upon which application is currently installed.

• If the EmailXaminer 2.1 client is installed, and the EmailXtender 4.7 Notes Search Plug-in is not installed, do the following:1. Locate the files eamgr.dll and OTGNotesAPI.dll. These files are installed in the

\Programs\Common Files\OTG directory. 2. Move these files to the installation directory of the EmailXaminer 2.1 client

where the file EmailXaminer.exe exists.You can now install the EmailXtender 4.7 Notes Search Plug-in on this computer.


Release Notes

29

• If the EmailXtender 4.7 Notes Search Plug-in is installed, and the EmailXaminer 2.1 client is not installed, do the following:1. Locate the files, eamgr.dll and OTGNotesAPI.dll. These files are installed in the

\Programs\Common Files\OTG directory. 2. Move these files to the installation directory of the EmailXtender 4.7 Notes

Search plug-in where the file ExSearch.exe exists.You can now install the EmailXaminer 2.1 client on this computer.

(SDR 11795)

Do Not Install Audit and EmailXaminer Manager on Same Computer

If you install EmailXtender Audit on the same computer where EmailXaminer Manager is installed, you cannot log in to the EmailXaminer Manager client. The Sync Rollup and Sample Now utilities also do not work.

To correct this problem, perform a Modify installation on the EmailXaminer Manager without changing any of the selections. (SDR 11532, 10821)

EmailXtender Clients Should Not Be Installed on EmailXaminer Server

Do not install EmailXtender clients, such as the Audit client or the Search Plug-in, or EmailXtract on the same computer as the EmailXaminer server. Doing so will cause problems in those applications. (SDR 39985, 8404, 40361, 8561)

PST Migration Feature Can Impact EmailXaminer Performance

EmailXtender 4.7 includes an enhanced capability to migrate Microsoft Outlook Personal Folder (.pst) files into the EmailXtender archive using EmailXtract. In most cases, the .pst files contain messages which existed prior to the implementation of EmailXtender.

If you are also using EmailXaminer in your environment, you should be aware that messages ingested during .pst migration that are associated with users being monitored by EmailXaminer are subject to sampling by EmailXaminer. Unless mitigated, and depending on the number of messages migrated during the .pst file processing, this can increase the message volume for these users, which in turn may increase the workload for reviewers configured in EmailXaminer. EmailXaminer Reviewers could also see messages with older dates sampled by EmailXaminer.

To mitigate the potential impact when migrating .pst files, LEGATO recommends that you do the following:

• Temporarily suspend EmailXtender journaling when doing the EmailXtract task to migrate the .pst files

• Suspend the connection between EmailXtender and EmailXaminer.


Release Notes

30

The following procedure should be coordinated between the EmailXtender administrator and the EmailXaminer administrator:

1. Remove the Microsoft Exchange journaling from the list of Email Connection Mailboxes in EmailXtender Administrator.

a. In the Tree view of the EmailXtender Administrator, right-click the EmailVault node and select Properties from the shortcut menu. The Vault Properties dialog box appears.

b. Select the Email Connection Mailboxes tab.

Note: Before performing the next step, record the mailbox name. You will need to re-establish the connection at the end of this procedure.

c. Select the connection mailbox and click Delete.

2. Ensure all journaled mail is processed by checking the message queues on the EmailXtender server. Refer to Chapter 6, Maintenance, in the EmailXtender Administrator’s Guide for information on checking message queues.

3. Remove the connection between EmailXtender and EmailXaminer by deleting three registry keys on the EmailXtender server.

a. Click Start>Run>regeditb. Navigate to the following location:

HKEY_LOCAL_MACHINE\SOFWARE\OTG\EmailXtender

c. Delete the following registry keys:- ExaminerEnabled- ExaminerMachineName- ExaminerVersion

4. Run the EmailXtract task to migrate the .pst files. Refer to Chapter 10, EmailXtract in the EmailXtender Administrator’s Guide for information on selecting and migrating .pst files.

5. Once the EmailXtract task has been completed, check the message queues on the EmailXtender to ensure all messages have been processed.

6. Reconnect EmailXaminer to the EmailXtender server using the RegisterXaminer utility:

a. Click Start > Programs > Legato EmailXaminer > RegisterXaminer. The Attach EmailXaminer to an EmailXtender Server dialog box displays.

b. Enter the EmailXtender server name or IP Address in the EmailXtender Server Name (or IP Address) field.

c. Click Register.

Note: Wait a few moments for registration to occur.

A success message is displayed.

7. Re-configure the mailbox connectors deleted in step 1. Refer to Chapter 3, Configuring Message Collection in the EmailXtender Administrator’s Guide for information on adding a mailbox connector.


Release Notes

31

Documentation Issues

The following are known issues or omissions in the EmailXtender documentation.

Missing Message Icon Blue Not Red

The missing message icon used by the EmailXtender Administrator and the HealthCheck utility has changed color from red to blue to make it more distinct from the corrupt index icon which is red. The documentation lists the missing message icon as being red. (SDR 12159)

Exporting Search Results to PST or NSF

When exporting results to PST or NSF files, the resulting files are placed in a dynamically-generated sub-directory within the output directory specified in the export settings. (SDR 12108)

Enhanced EmailXtender Language SupportEmailXtender supports the processing of messages and attachments in a variety of languages. This support includes the use of EmailXender on German and French software versions, providing selected local language strings for the Search Plug-in and the Web Search client, and processing messages and attachments in Western and Central European languages.

This information supersedes the information in the EmailXtender Installation Guide.

These capabilities are discussed in the following sections.

• "Support for German and French Language Environments" on page 31• "Selected Local Language Strings For Search Clients" on page 32• "Characters Supported in Messages and Attachments" on page 33

Support for German and French Language Environments

The EmailXtender server can be installed in the German and French language environments listed in the following table on German or French operating systems, respectively.


Release Notes

32

See your mail server or mail client documentation for the supported operating system versions for the mail server or mail client.

When any EmailXtender component is installed on French or German language versions of Windows, the component must be installed using the default path provided by the installation wizard. Installation paths and SQL database names and paths cannot include any extended characters (characters with values greater than 128).

In addition, no EmailXtender name fields should use extended characters. Such fields include EmailXtender rules, service account names, folder names, and so on. Do not use a mailbox with a user name or display name that uses extended characters for the EmailXtender MAPI profile or for the mailbox connector used for journaling. If you do so, you could lose the connection to the mail server services. Similarly for Notes, do not use an EmailXtender Notes user name that uses extended characters.

Selected Local Language Strings For Search Clients

EmailXtender supplies local language strings for use in the Web Search client and the Search Plug-in for the following non-English languages:

• German• French• Spanish• Italian

Table 2. Supported German and French EmailXtender Configurations

Mail Server Mail ClientEmailXtender Server OS

EmailXtender Database

German Exchange 2000 German Outlook 2000 or 2003

German Windows 2000or Windows 2003

German SQL Server 2000, Standard or Enterprise edition

German Exchange 2003

German Domino 5.0.2a-5.0.13 German Notes 5.0.2a-5.0.13, 6.0-6.0.4, 6.5-6.5.3

German Domino 6.0-6.0.4

German Domino 6.5-6.5.3

French Exchange 2000 French Outlook 2000 or 2003

French Windows 2000or Windows 2003

French SQL Server 2000, Standard or Enterprise edition

French Exchange 2003

French Domino 5.0.2a-5.0.13 French Notes 5.0.2a-5.0.13, 6.0-6.0.4, 6.5-6.5.3

French Domino 6.0-6.0.4

French Domino 6.5-6.5.3


Release Notes

33

Characters Supported in Messages and Attachments

EmailXtender supports the use of a large number of languages in messages and attachments.

• The LATIN-1 character set is supported and includes languages such as English, German, French, Spanish, Italian, Danish, and Swedish. For more information, see "LATIN-1 Character Support" on page 33.

• The LATIN-2 character set is supported with some restrictions and includes languages such as Czech, Hungarian, Polish, Croatian, Romanian, Slovak, and Slovenian. For more information, see "LATIN-2 Character Support" on page 34.

• "Guidelines on Using EmailXtender with LATIN-1, LATIN-2, or MBCS Characters" on page 35.

• Japanese and Simplified Chinese are supported with some restrictions. For more information, see "Japanese and Simplified Chinese Language Support" on page 38.

LATIN-1 Character Support

The LATIN-1 character set is supported for messages and attachments and includes languages such as English, German, French, Spanish, Italian, Danish, and Swedish. You use the LATIN-1 character set by setting the Windows default language code page to Windows code page 1252; this is the default language code page for the LATIN-1 language versions of Windows. The following table lists the major EmailXtender capabilities and the support for those capabilities using the LATIN-1 character set with the designated mail server.

Table 3. Support for Messages and Attachments Using LATIN-1 Characters

Message Can Be

Mail Server Type

Exchange Domino SMTP

Ingested by (brought into) EmailXtender Yes1 Yes Yes

Archived by EmailXtender Yes Yes Yes

Indexed by EmailXtender Yes Yes Yes2

Searched Using Search Plug-in or Web Client Yes3 Yes3 Yes2

Shortcut Using EmailXtract Yes1 Yes Non-applicable


Release Notes

34

LATIN-2 Character Support

The LATIN-2 character set is supported with some restrictions and includes languages such as Czech, Hungarian, Polish, Croatian, Romanian, Slovak, and Slovenian. You use the LATIN-2 character set by setting the Windows default language code page to Windows code page 1250; this is the default language code page for the LATIN-2 language versions of Windows. The following table lists the major EmailXtender capabilities and the support for those capabilities using the LATIN-2 character set with the designated mail server.

Displayed Using Mail Client or EmailXtender Yes3 Yes3 Yes2

1Folder names containing multi-byte characters cannot be processed by EmailXtract.2SMTP messages use a restricted character set that causes characters with values higher than 128 to not be searchable or to not display properly. Opening these messages in an email client allows those messages to be displayed properly. For more information, see "Using SMTP Messages with LATIN-1 or LATIN-2 Characters" on page 36.3When you perform a search or display a search result using EmailXtender, you use the default language code page of the computer running the Search Plug-in or Web Search client to determine what character set to use. For more information, see "Searching Messages Using Different Character Sets" on page 36.


Message Can Be

Mail Server Type


Ingested by (brought into) EmailXtender Yes1 Yes Yes

Archived by EmailXtender Yes Yes Yes

Indexed by EmailXtender Yes Yes2 Yes3

Searched Using Search Plug-in or Web Client Yes4 Yes2,4 Yes3

Shortcut Using EmailXtract Yes1 Yes Non-applicable


Message Can Be

Mail Server Type



Release Notes

35

Guidelines on Using EmailXtender with LATIN-1, LATIN-2, or MBCS Characters

The following are guidelines in using EmailXtender with messages or attachments that contain LATIN-1, LATIN-2 or multi-byte characters. The following sections contain information you should be aware of when using differing character sets.

• "System Requirements for LATIN-2 Support" on page 35• "Using SMTP Messages with LATIN-1 or LATIN-2 Characters" on page 36• "Using Messages with Multiple Languages and LATIN-2, MBCS or LMBCS

Characters" on page 36• "Searching Messages Using Different Character Sets" on page 36• "Displaying Messages Using Different Character Sets" on page 37• "Indexing LATIN-1 and LATIN-2 Messages Using a Single EmailXtender Server"

on page 37

System Requirements for LATIN-2 Support

The following are some additional configuration changes you may need to make to support LATIN-2 languages with EmailXtender:

• To support Exchange indexing and searching of LATIN-2 attachments, the language code page for LATIN-2 must be installed on the EmailXtender server. However, it does not need to be the default language code page.

• When you install the EmailXtender Search Plug-in for use with LATIN-2 language versions of Microsoft Outlook or Notes, you must install the Search Plug-in to the default path provided by the installation wizard. The install path cannot include any directory or filename that includes extended characters (those characters with values greater than 128).

Displayed Using Mail Client or EmailXtender Yes4 Yes4 Yes3

1Folder names containing multi-byte characters cannot be processed by EmailXtract.2The default language code page for the EmailXtender server must be set to LATIN-2 for Notes to process LATIN-2 messages properly. This will cause some LATIN-1 extended characters (those with values higher than 128) to be indexed incorrectly.3SMTP messages use a restricted character set that causes characters with values higher than 128 to not be searchable or to not display properly. Opening these messages in an email client allows those messages to be displayed properly. For more information, see "Using SMTP Messages with LATIN-1 or LATIN-2 Characters" on page 36.4When you perform a search or display a search result using EmailXtender, you use the default language code page of the computer running the Search Plug-in or Web Search client to determine what character set to use. For more information, see "Searching Messages Using Different Character Sets" on page 36.


Message Can Be

Mail Server Type



Release Notes

36

Using SMTP Messages with LATIN-1 or LATIN-2 Characters

SMTP messages use a restricted character set, and so extended LATIN-1 or LATIN-2 characters (character values greater than 128 in either character set) in the message subject or body will not be searchable or displayed properly using the Search Plug-in or the Web Search Client.

Characters in the Date field are searchable and are displayed properly.

Characters in the From or Sent To fields are searchable and are displayed properly if they do not contain any extended characters (characters with values greater than 128). Searching by the SMTP address will ensure that no such characters are encountered. Opening these messages in an email client allows those messages to be displayed properly.

Using Messages with Multiple Languages and LATIN-2, MBCS or LMBCS Characters

Messages containing multiple languages, when all those languages use LATIN-1 characters, are archived and indexed correctly using a LATIN-1 character set. Similarly, messages containing multiple languages, when all those languages use LATIN-2 characters, are archived and indexed correctly using a LATIN-2 character set.

However, if LATIN-1 and LATIN-2 languages are mixed in the same message, or if multi-byte characters are part of a message that contains LATIN-1 or LATIN-2, such as a Japanese language attachment to a Czech language email message, the message is archived correctly but is incorrectly indexed.

• If the message is sent from an Exchange mail server, the message is indexed using the encoding system property found in the MAPI properties of the message.

• If the message is sent from a Domino mail server, the message is converted from the Lotus Multi-Byte Character Set (LMBCS) character set to the default code page of the EmailXtender server and indexed using that code page.

• If the message is sent from an SMTP mail server, the message is not converted.

Searching Messages Using Different Character Sets

When you perform a search using EmailXtender, you use the default language code page of the computer running the Search Plug-in or Web Search client to determine what character set to use. If the default language code page is set to LATIN-1 (Windows code page 1252), then you can search in any of the LATIN-1 languages. For example, you could search in French, German, or Italian from the same Search Plug-in.

However, you cannot search in a language that requires a different default language code page than the one set on the client computer. For example, you cannot search Polish text (which uses the LATIN-2 characters in Windows code page 1250) from a computer where LATIN-1 is the default language code page. To search LATIN-2 messages, set the default language code page to LATIN-2 and then perform the search.

If you attempt to enter LATIN-2 characters in any Search Plug-in field while the default language code page is set to LATIN-1, the characters will be entered as LATIN-1 characters.


Release Notes

37

In addition, if you are using the Exchange Search Plug-in from a system where the default language code page is set to LATIN-2 and you click the From, Sent To, or Mailbox buttons to select an email address from the Exchange global address list (GAL) that contains LATIN-2 extended characters, those characters will not be processed correctly by an EmailXtender server running with the default language code page set to LATIN-1. This problem would also occur if the Search Plug-in was running on a LATIN-1 system and the EmailXtender server was running on a LATIN-2 system.

To work around this problem, enter the SMTP or canonical form of the email address rather than picking the display name from the address list.

Displaying Messages Using Different Character Sets

When you view a message using the EmailXtender Search Plug-in or the Web Search client, you view the message using the default language code page of the computer on which you are running the Search Plug-in or Web Search client, regardless of the code page with which the message was created. If the message, or part of the message such as the subject or attachment file name, is displayed incorrectly, it indicates that EmailXtender cannot display the characters correctly using the default language code page.

If the message is from a Domino or Exchange server, open the message in Notes or Outlook to view the message correctly. Messages opened in Outlook or Notes do not use the default language code page and so can be viewed properly. Alternatively, to display the foreign characters correctly with EmailXtender, set the foreign language as the default language for the client computer and then open the message using the Search Plug-in or Web Search client.

Indexing LATIN-1 and LATIN-2 Messages Using a Single EmailXtender Server

EmailXtender can index multiple character sets in an Exchange mail server environment, and with some limitations in a Domino mail server environment. This allows you to have a single EmailXtender server handle messages in Polish (LATIN-2) as well as messages in English and German (LATIN-1).

• EmailXtender indexes Exchange messages using the character set property of individual messages. Because of this, EmailXtender can index Exchange messages containing either LATIN-1 (code page 1252) or LATIN-2 (code page 1250) characters using a single EmailXtender server with a default code page of LATIN-1.

• EmailXtender indexes Domino messages using the default language code page of the EmailXtender system. Because of this, EmailXtender can correctly index only Domino messages that use the same characters as the default language code page. Characters from other code pages will not be indexed correctly and so those characters will not be searchable.For example, when EmailXtender is installed on a system where the default language code page is set to LATIN-1, such as the English, French, and German language versions of Windows, EmailXtender cannot index characters in Domino messages that are unique to the LATIN-2 character set correctly.


Release Notes

38

To index LATIN-2 characters in Domino messages correctly, install the LATIN-2 language code page on the EmailXtender system and change the default language code page of the EmailXtender server to LATIN-2. English and German character sets will not be affected by this change since their characters are part of both the LATIN-1 and LATIN-2 character sets.Changing the default language code page to LATIN-2 will cause some LATIN-1 characters to not be indexed and not be searchable: in this environment, Spanish has 2 unsearchable characters (including upper and lowercase versions), Italian has 12 unsearchable characters, and French has 16 unsearchable characters.Also, you should verify that none of the EmailXtender name fields use LATIN-1 or LATIN-2 extended characters (values 129 or higher) or use any multi-byte characters. Such fields include EmailXtender rules, service account names, folder names, and so on.

Japanese and Simplified Chinese Language Support

You can use EmailXtender to process Japanese and Simplified Chinese messages that have been sent or received by Japanese or Simplified Chinese versions of Microsoft Outlook 2000 or Microsoft Outlook XP installed on the corresponding language versions of Microsoft Windows 2000 or Microsoft Windows XP. EmailXtender allows you to archive and search Japanese messages encoded by JIS, Shift-JIS, JIS-Allow 1 byte Kana, EUC, and Simplified Chinese messages encoded by GB2312 and HZ.

For more information on Japanese and Simplified Language support, see the following sections:

• "System Requirements for Japanese or Simplified Chinese Support" on page 38• "Processing Japanese or Simplified Chinese Multi-byte Messages" on page 39• "Processing Japanese or Simplified Chinese UTF-8 or UTF-7 Messages" on page 40

System Requirements for Japanese or Simplified Chinese Support

To archive, index, and search for messages that use Japanese or Simplified Chinese multi-byte characters, the system must meet the following requirements:

• The EmailXtender server must be using an English-language version of Windows 2000. Do not install EmailXtender on a Japanese or Chinese language version of the Windows operating system.

• The mail server must be an English language version of either Microsoft Exchange 5.5 or 2000 running on an English language version of Windows 2000, and the appropriate language code pages must be installed on the mail servers and the domain servers for those mail servers, as described in the Microsoft Exchange documentation.

Note: Lotus Domino and Microsoft Exchange 2003 are not supported with the use of Japanese or Simplified Chinese multi-byte character sets.


Release Notes

39

• To support indexing and searching of attachments, such as Word 2000 documents containing Japanese, install the language code pages for these languages on the EmailXtender server as follows:1. Log on to the EmailXtender server as Administrator. 2. From the Start menu, select Settings>Control Panel. 3. Double-click Regional Options. 4. On the General tab, under Language settings for the system, select the

appropriate language check box, such as Japanese.5. Insert the Windows 2000 Server CD-ROM to complete the installation. 6. Restart the computer.

• When you install the EmailXtender Search Plug-in for use with Japanese or Chinese language versions of Microsoft Outlook, you must install the Search Plug-in to the default path provided by the installation wizard. The install path cannot include any directory or filename that includes multi-byte characters.

• Do not use a mailbox with a display name that uses multi-byte characters for the EmailXtender MAPI profile or for the mailbox connector used for journaling. If you do so, you could lose connection to the mail server services.

Any additional requirements for Japanese or Simplified Chinese multi-byte character support are noted in the EmailXender Installation Guide, the EmailXtender Administrator’s Guide, and the EmailXtender Search User’s Guide where they are applicable.

Processing Japanese or Simplified Chinese Multi-byte Messages

When EmailXtender processes multi-byte character set messages, the following occurs:

1. EmailXtender determines the language of each message according to the code page properties for the message.

2. EmailXtender creates a language code-specific profile with the form, exJournal-Language-codepage (for journaling) or exExtract-Language-codepage (for EmailXtract), and assigns it to the message when it is archived.

For example, if EmailXtender receives a message with the Japanese code page property while it is collecting mail through journaling on a Microsoft Exchange server, EmailXtender creates a profile such as exJournal-Japanese-932.

3. EmailXtender automatically creates a separate volume for each language it archives; all messages containing the same language are stored in the same volume. A volume for each language contains a 0 byte file with the form LanguageName.Lang, which specifies the language the index service uses to index messages in the volume. For example, for messages containing Japanese, the file that specifies the language is Japanese.Lang.

4. EmailXtender then indexes each language-specific volume. For more information on how EmailXtender full-text indexes other languages, refer to the Introduction chapter in the EmailXtender Administrator’s Guide.


Release Notes

40

Processing Japanese or Simplified Chinese UTF-8 or UTF-7 Messages

EmailXtender can archive and index Unicode (UTF-8 or UTF-7) encoded Japanese and Simplified Chinese messages if the messages originate from a corresponding Japanese or Chinese version of a Windows operating system. If the messages originate from operating systems whose default languages are different from those of the messages, then EmailXtender cannot determine their language properties to archive and index them correctly. The occurrence of receiving such messages is exceptionally rare. However, the following preventative measures protect the messages from being incorrectly archived:

• If you are archiving messages in real-time using journaling, EmailXtender moves the messages to an Unknown Language folder under the Sent Items folder of the mailbox connector. You must manually process the messages.

• If you are archiving messages using the Archive task in EmailXtract, EmailXtract does not archive the messages; EmailXtract skips these messages and logs errors indicating that UTF-8/UTF-7 messages without proper code page information have been found.

Documentation AdditionsDocumentation for the following topics was created late in the development cycle and so appears in this document. This information will be added to the appropriate documentation in a future release.

• "Conducting Wildcard Domain Address Searches on External Contacts" on page 40

• "Assigning Owners to Messages Using EmailXtract" on page 41• "Identity Management Guidelines for EmailXtender" on page 41

Conducting Wildcard Domain Address Searches on External Contacts

In Microsoft Exchange, an administrator can add a contact with an external email address to the Global Address List (identified as Contact in the Type field of the Active Directory Users and Computers dialog box). When EmailXtender archives messages addressed to this external contact, only the canonical form of the address is stored. The external contact's SMTP address is not part of the domain in the canonical address. Therefore, when a wildcard address search is conducted using the Search Plug-in on a portion of the SMTP address for the contact (such as *.outsidecompany.com), messages for this contact are not returned.

To ensure that search results are captured for this external contact as part of a domain search, LEGATO recommends that users conducting searches specify the canonical display name for each external contact in order to return more complete results. For example, if [email protected] is in the global address list as an external contact, a search for messages sent to the domain outsidecompany.com should contain both *@outsidecompany.com and John Smith selected from the address book (to include the full canonical address in the search query).


Release Notes

41

Assigning Owners to Messages Using EmailXtract

Messages journaled and archived in real-time using EmailXtender have complete ownership information associated with them. Messages archived using EmailXtract have less ownership information available because the data about those messages is historical and not as current as the data from journaled messages.

For example, messages that are journaled and archived have their distribution lists expanded, and all members of the distribution list are listed as owners of the message. If a message sent to a distribution list is archived by EmailXtract, EmailXtract does not expand that distribution list because the message may have been sent to a different version of the distribution list (with different members) than the current version.

EmailXtender 4.7 makes it possible to add more ownership information to messages archived using EmailXtract and so increase the completeness and accuracy of ownership information for those messages.

Owners are automatically assigned to messages, if needed, when the EmailXtract Archive or Shortcut tasks process messages. Owners can also be manually assigned to messages in a PST file using the EmailXtract PST Selection tab.

When the owners are added to the index depends on the version of EmailXtender that created the index:

• If it is an index created by EmailXtender 4.7:The owners are automatically added to the index and will be immediately searchable.

• If it is an index created by a previous version of EmailXtender:The owners are automatically stored in the SQL database, but they are not searchable until the volume is re-indexed by EmailXtender 4.7.

Identity Management Guidelines for EmailXtender

To conduct effective and complete compliance or legal discovery searches on a specific person, all known variations of the system identifiers associated with the person must be available for use as search criteria.

When executing searches, EmailXtender uses the address information stored in the current global address book for the mail environment. Because EmailXtender does not programatically maintain historical address information, it is up to companies to manage this information themselves. This document provides recommendations on how to maintain this information and conduct effective compliance or legal discovery search results.

What Is Identity Management?

In a typical environment, users are added and deleted from global address books on a daily basis. In addition, email address information for a user can change over time due to name changes, company mergers and acquisitions, the use of aliases, and other factors. Identity management consists of managing the correlation between a real person and the system identifiers associated with this person over time.


Release Notes

42

These recommendations assume that you are starting from a particular point in time and want to set up a methodology to capture and manage historical address information going forward. For environments that require assistance with discovering historical address information over a specific period of time in the past, contact LEGATO Professional Services.

Managing Historical Address Information

Your company should employ a methodology to track when former employees are removed from the Global Address List (GAL) in Microsoft Exchange, or the Name and Address Book (NAB) in Lotus Domino. You should also track changes to user address information which occur over time (for example, domain name changes due to company mergers, name changes, email address formatting changes, and so on). At a minimum, the methodology should involve recording the following information:

• Name• Employee ID• All address forms used and effective dates for each

For example, address information for a Lotus Domino user named John Doe could include the SMTP, domain and canonical forms of the address shown below:

• SMTP - [email protected], [email protected]• Domain - John Doe/Boston/Legato/EMC• Canonical - CN=John Doe/OU=Boston/OU=Legato/O=EMC

Similarly, address information for a Microsoft Exchange user named John Doe could include the SMTP, canonical/Distinguished Name, and X.500/Distinguished Name forms of the address as shown below:

• SMTP - [email protected], [email protected]• Canonical/Distinguished Name -

/O=EMC/OU=Legato/OU=Boston/CN=recipients/CN=JohnDoe• X500/Distinguished Name -

/O=EMC/OU=Legato/OU=Seattle/CN=recipients/CN=JohnDoe

Configuring Legacy Addresses for Existing Users

For users who still exist in the Microsoft Exchange GAL or Lotus Domino NAB, you can include other known addresses as a legacy address in the properties of the corresponding user on the mail server. When EmailXtender executes a search, it automatically includes the legacy address information in the search.

For example, if employee Jane Doe marries and changes her name to Jane Smith, you can make the name change to [email protected] in the GAL or NAB and add the legacy address [email protected] to the properties for Jane Smith on the mail server. Subsequent searches on [email protected] will return email addressed to both [email protected] and [email protected].


Release Notes

43

Configuring Legacy Addresses in Microsoft Exchange

To add legacy email address information for a user in Microsoft Exchange:

1. Log in to the domain with an account that has Exchange administrator rights, and view the properties of the user to whose profile you want to add a legacy address.

• If you are using Windows 2000 and Active Directory, you can access user properties by selecting Active Directory Users and Computers from the Administrative Tools menu, expanding the Users node (beneath the domain server node), and double-clicking on a user name.

• If you are using standard NT networking, you can access user properties by selecting the User Manager for Domains snap-in from the Administrative Tools menu, and double-clicking on a user name.

2. Activate the E-mail Addresses tab and click the New button. The New E-mail Address dialog box appears.

3. Open the Other Address Properties dialog box.

• If you are using Exchange 5.5, select Other Address and click OK.• If you are using Exchange 2000, select Custom Address and click OK.

4. In the E-mail address text box, enter the user’s legacy address.

5. In the E-mail type text box, enter LEGACY.

6. Click OK.

7. Repeat the previous steps for additional legacy addresses you want to include.

Configuring Legacy Addresses in Lotus Domino

To add legacy email address information for a user in Microsoft Exchange:

1. From the Start menu, select Programs >Lotus Applications > Lotus Domino Administrator.

2. Enter the password when prompted. The Domino Administrator opens.

3. Click the People and Groups tab.

4. Expand Domino Directories, and then expand the address book.

5. Click People. Contacts should appear in the main pane.

6. Double-click the user to whose profile you want to add a legacy address. The person record appears, starting with the Basics tab.

7. Double-click within the Short name/User ID area so that it becomes editable.

8. Move to a new line, and enter the legacy address.

9. Click Save and Close to save changes and return to the Administration - People & Groups page.

Conducting Effective Searches

For detailed information, including considerations and recommendations related to conducting effective searches using the EmailXtender Search Plug-in or the Web Search client, refer to the EmailXtender Search User’s Guide.


Release Notes

44

Documentation ImprovementsThe EmailXtender documentation suite was reorganized to be more task-based and user-friendly. Similar types of information were combined to reduce the core documentation set from eight guides to three. The Online Help was also enhanced to focus the content on the selected component.

In addition, additional best practices information has been added on several subjects, including how to:

• Regularly maintain an EmailXtender server• Troubleshoot problems in the EmailXtender environment• Configure antivirus software with EmailXtender• Install and configure DiskXtender for use in an EmailXtender environment

The following sections provide an introduction to the revised documentation suite and include an overview of each chapter so that you can familiarize yourself with where certain types of information are located:

• "EmailXtender Installation Guide" on page 44• "EmailXtender Administrator’s Guide" on page 45• "EmailXtender Search User’s Guide" on page 46• "Online Help" on page 46

LEGATO welcomes comments and suggestions about the documentation. To provide suggestions and comments, send e-mail to [email protected]. To help improve our documentation in general, complete a brief survey at www.legato.com. Navigate to the documentation page and click the link to the survey. Although LEGATO cannot respond personally to every request, all comments and suggestions are considered during product design.

EmailXtender Installation Guide

The EmailXtender Installation Guide contains the following chapters:

• Chapter 1: Introduction -- This chapter covers system architecture, system components (including EmailXtender server components, mail server components, client components, and optional add-ins), EmailXtender concepts (including message collection, message archival, and system management), EmailXtender Archive Edition limitations, and an overview of the installation process.

• Chapter 2: Planning the Installation -- This chapter covers system requirements for the EmailXtender server, mail server, and client computers, as well as EmailXtender system language support.

• Chapter 3: Installing EmailXtender -- This chapter covers pre-installation steps, how to install EmailXtender server components, how to install EmailXtender client components, and how to uninstall EmailXtender.

• Chapter 4: Updating EmailXtender -- This chapter covers how to update EmailXtender, including steps to take before the update, how to perform the update, and how to run the database upgrade utility.

• Chapter 5: Licensing EmailXtender -- This chapter covers how to install License Server, obtain a product license, add the license, and change license configuration.



Release Notes

45

• Chapter 6: Microsoft Exchange Journaling and Shortcut Support -- This chapter covers how to set up Microsoft Exchange 5.5, 2000, and 2003 servers so that you can journal mail to EmailXtender and enable shortcut support for Microsoft Outlook and OWA users.

• Chapter 7: Lotus Domino Journaling and Shortcut Support -- This chapter covers how to set up Lotus Domino servers running on the Microsoft Windows, Sun Solaris, Red Hat Linux, IBM AIX, or IBM AS/400 operating systems so that you can journal mail to EmailXtender, and enable shortcut support and $Reader field support for Lotus Notes users.

• Chapter 8: MilVault -- This chapter covers how to install the MilVault milter and archiver so that you can archive mail from a sendmail server. It includes how to test MilVault communication with sendmail, troubleshoot installation, configure MilVault, start MilVault manually, and uninstall MilVault.

EmailXtender Administrator’s Guide

The EmailXtender Administrator’s Guide contains the following chapters:

• Chapter 1: Introduction -- This chapter covers system architecture, Message Center architecture, EmailXtender concepts (including message collection, message archival, and system management), EmailXtender Archive Edition limitations, and an overview of how to configure EmailXtender after you install it.

• Chapter 2: Using the EmailXtender Administrator -- This chapter covers how to start and use the EmailXtender Administrator interface, remotely administer the EmailXtender system, and auto-size columns, refresh, and activate changes in the Administrator interface.

• Chapter 3: Configuring Message Collection -- This chapter covers how to plan and configure the Message Center architecture, including vault, cabinet, and folder properties.

• Chapter 4: Rules -- This chapter covers how to create, edit, and delete EmailXtender rules, use external message rules, and use LDAP/ADS filters.

• Chapter 5: Configuring Message Archival -- This chapter covers how to manage volumes individually and by month, configure volume storage using the Computer Properties dialog box, and configure DiskXtender for use with EmailXtender.

• Chapter 6: Maintenance -- This chapter contains an overview of message processing, and covers maintenance tasks, events, utilities, and how to edit EmailXtender account information.

• Chapter 7: Troubleshooting -- This chapter covers how to troubleshoot message collection, volumes, shortcuts, searches, the EmailXtender server, and other issues, as well as how to get help if you are not able to resolve the problem.

• Chapter 8: Controlling Searches -- This chapter covers how to control search access using supervisor groups, administrator searches, and directed searches.

• Chapter 9: EmailXtender Audit -- This chapter covers how to monitor supervisor and administrator search and deletion activity using the EmailXtender Audit Utility.

• Chapter 10: Archiving Bloomberg Mail -- This chapter covers how to use the Bloomberg Mail Parser to archive Bloomberg Mail to EmailXtender.


Release Notes

46

• Chapter 11: EmailXtract -- This chapter covers how to use the EmailXtract component to configure Archive, Shortcut, Delete, Search, and Analysis tasks.

• Appendix A: Expression Operators -- This appendix covers expression operators, such as AND, OR, NOT, wildcards, and parentheses, which you can use to further focus the results of searches and keyword rules.

• Glossary -- The glossary lists commonly used EmailXtender terms.

EmailXtender Search User’s Guide

The EmailXtender Search User’s Guide contains the following chapters:

• Chapter 1: Introduction -- This chapter covers the differences between the Web Search Client and the Search Plug-in, the types of searches you can perform in EmailXtender, and an overview of EmailXtender search concepts.

• Chapter 2: Web Search -- This chapter covers how to start, configure, and create a basic search using the Web Search Client, as well as what you can do with search results.

• Chapter 3: Search Plug-in -- This chapter covers how to start, configure, and create a basic search using the Search Plug-in, as well as what you can do with search results.

• Chapter 4: Entering Email Address Search Criteria -- This chapter contains tips on entering email addresses in the From, Sent To, and Mailbox fields of the search tools, as well as using wildcards in those fields if you have administrator privileges and you are using the Search Plug-in.

• Chapter 5: Entering Keyword Search Criteria -- This chapter contains tips on entering keywords in the Search for the Word(s) field of the search tools, including using Boolean operators, using positional operators, entering multiple words, using wildcards, using tense conflation, understanding how the search handles different character types, handling reserved words, and controlling search processing order using parentheses.

• Chapter 6: Advanced Search Criteria -- This chapter contains tips on entering advanced search criteria, such as setting a maximum number of search results, on the More Choices tab of the Search Plug-in or the Advanced Settings dialog box of the Web Search Client.

Online Help

EmailXtender, Release 4.7 provides the following Online Help files:

• EmailXtender Administrator Online Help -- This Online Help file, available from the EmailXtender Administrator interface, covers how to use the EmailXtender Administrator interface to configure and maintain the system, including the Message Center architecture, rules, volume management, maintenance tasks, and troubleshooting.

• EmailXtract Online Help -- This Online Help file, available from the EmailXtract Administrator interface, covers how to use the EmailXtract Administrator interface to configure tasks and manage task results.


Release Notes

47

• EmailXtender Search Plug-in Online Help -- This Online Help file, available from the Search Plug-in, covers how to start, configure, and create a basic search using the Search Plug-in, as well as what you can do with search results. It also covers how to enter search criteria.

• EmailXtender Web Search Client Online Help -- This Online Help file, available from the Web Search Client, covers how to start, configure, and create a basic search using the Web Search Client, as well as what you can do with search results. It also covers how to enter search criteria.

• EmailXtender Audit Utility Online Help -- This Online Help file, available from the Audit Utility interface, covers how run standard and custom audit reports, as well as what you can do with the resulting reports.

• EmailXtender HealthCheck Utility Online Help -- This Online Help file, available from the HealthCheck Utility interface, covers how to use the HealthCheck utility to verify that all messages were archived, verify that messages are not missing from a volume, and rebuild a corrupt month or index.