Lotus Protector for Mail Encryption 2.1.0.1 What's Been Fixed

This document contains description of what's been fixed in the Lotus Protector for Mail Encryption fixpack version 2.1.0.1.

Note that the documentation set for this fixpack is available electronically from the "Lotus Protector for Mail Encryption documentation" page in the devWorks Technical Library.
Lotus Protector for Mail Encryption Version 2.1.0.1 Resolved Issues
Resolved issues include the following:

General
 Significant improvements have been made to the performance of the Lotus Protector for Mail Encryption Server in a number of important areas.

 Fixed an issue that caused the server to become unresponsive to client requests, requiring services to be restarted.

 Fixed a problem that allowed a redirect from the Lotus Protector for Mail Encryption Server User Interface to a page outside the Lotus Protector for Mail Encryption Server, when using a browser with JavaScript disabled.

Installation/Upgrade/Migration
 Fixed a problem that caused the "expert" option of the Lotus Protector for Mail Encryption Server Installation function to fail.

 After an upgrade to Lotus Protector for Mail Encryption Server 2.1.0.1, excluded users are correctly included in the Everyone group in the Administrative Console.

 After an upgrade to Lotus Protector for Mail Encryption Server 2.1.0.1, consumers that are members of groups that do not have an associated consumer policy are now correctly displayed.

Lotus Protector for Mail Encryption Client
 When a mail policy is configured to use the “Bounce Message” action, the Lotus Protector for Mail Encryption client will no longer prompt the user to cancel or to send in the clear. If the policy is to block the message, the Lotus Protector for Mail Encryption client will just block the message.

 When a mail policy specified a pattern match to an attachment named in a Lotus Notes RTF message, the match would fail. This has been fixed.

 When a Lotus Notes user ID uses non-ASCII characters, the “Sender in Dictionary” condition would fail to identify the name as a match. This has been corrected.

LDAP Directory Synchronization
 When searching for a consumer in all ordered LDAP directories, and the consumer is not found in the first searched directory, the search now continues to the other ordered directories, even when LDAP referrals are enabled.

 Lotus Protector for Mail Encryption Server now correctly follows LDAP referrals for directory synchronization.

 Fixed a problem that could cause client connections using LDAP authentication to deadlock.

 A user's Lotus Notes ID is no longer removed when an LDAP synchronization occurs.

Messaging
 Fixed an issue that caused periodic mail gateway crashes.

 In some instances, after a migration to Lotus Protector for Mail Encryption Server 2.1.0.1, an error was raised when modifying or adding custom policies. This has been fixed.

PDF Messenger
 Emails sent through PDF Messenger that contain already encrypted PDF documents in addition to other attachments, are now properly encrypted without requiring selection of the "Encrypt body text and all attachments" option for the PDF Messenger action.

Reporting
 The performance of a query for a large data set has been improved. However, if a query still takes too long, it will now time out with an error: "An unexpected error has occurred. Please check the logs for details."

Logging/Alerts
 Client connections were timing out, causing error messages to fill the error log. These connections no longer time out under normal circumstances.

Clustering
 Significant improvements have been made to PGP Universal Server clustering to enable support for large numbers of internal and external users. Performance has been significantly improved as well.

 In some instances, cluster nodes designated as DMZ nodes without private keys could not be correctly backed up and restored. This has been fixed.

 Use of a secondary NIC for cluster communication is now supported.

 The hosting of private keys on cluster members that are internal nodes cannot be disabled. Private key hosting can only be disabled on cluster members that are located in the DMZ.