Netmail Archive 5.4
Netmail Search 5.4
Along with enabling the legal hold feature in the Netmail Administration Console, you can also modify how Netmail Search behaves when a case requiring legal hold is saved. For example, in some organizations, legal hold is applied only to archived data, meaning that it is not necessary for litigation hold to be enabled on the Exchange mail system as well. In such cases, administrators may want to modify the behavior of Netmail Search when legal hold is enabled for a case. This can be done through the xgwxmlv.cfg file.
To modify the behavior of Netmail Search when legal hold is enabled for a case, follow these steps:
1. Navigate to the C:\Program Files (x86)\Messaging Architects\RemoteProvider folder, and open the xgwxmlv.cfg file.
2. Scroll down towards the end of the file and locate the
analytics.legalHoldRetention parameter performs a litigation hold retention check on Exchange. Change the value of this parameter to reflect how you want Netmail Search to behave when a Case Manager enables legal hold for a case. The following options are available to you:
force: The case will not be saved if litigation hold on the mailbox(es) on the Exchange Server for an account within the case has not been enabled. This ensures that any mail that has not yet been archived will not be omitted. This is the default (and recommended) value for this parameter.
warning: A warning about legal hold preventing the deletion of archived content from users' archives within the current case is displayed. The Case Manager is still able to save the case.
skip: The verification of litigation hold retention on Exchange is skipped altogether. This can speed up the legal hold process, but may be risky if proper retention settings on Exchange have not been set.
If any value other than the ones listed above is entered, the behavior will default to
Warning: Selecting the
skip values may result in gaps data retention, as live mail is not saved. It is strongly recommended that the default
force value is chosen.
4. Save the file.
5. Restart Remote Provider services.