Enabling/disabling and configuring Notes "Active Mail" processing
Active Mail processing is an optional feature that can detect and convert Notes rich-content features whereby messages carry live or active functional content. For information about Active Mail, see Migrating Notes “Active Mail” in chapter 3 of the Migrator for Notes to Exchange Pre-Migration Planning Guide.
The MNE Data Migration Wizard provides options to enable/disable and configure Active Mail processing. In the SSDM you can enable and configure these features using program parameters in the notesdtapp.ini file. Active Mail processing is disabled by default (if the parameters are omitted from notesdtapp.ini).
To enable and configure Active Mail processing in SSDM, set the following parameters in the notesdtapp.ini file:
|
• |
[Notes] MigrateActiveMail=<#> Boolean; default = 0 Determines whether Migrator for Notes to Exchange's Active Mail features are enabled (1) or disabled (0). |
|
• |
[Notes] ActiveMailTemplatePath=<string> String; default = <Migrator for Notes to Exchange installation directory>\ActiveMail.ntf Specifies the full path including the filename of the MNE Active Mail template file. This file provides the information necessary for MNE to process the Notes OND attachment and produce the Active Mail attachment file. MNE installs a default ActiveMail.ntf to the installation directory, and that path is the default string for this parameter. However, you can specify a different path. |
|
• |
[Notes] ActiveMailNotificationMessagePath=<string> String; default = <Migrator for Notes to Exchange installation directory>\ActiveMailNotificationMessage.txt Specifies the full path including the filename of the MNE Active Mail notification message text file. The SSDM inserts the contents of this file at the top of the body of any migrated message containing Active Mail. MNE installs a default file, ActiveMailNotificationMessage.txt, to the installation directory and that path is the default string for this parameter, However, you can specify a different path. |
|
NOTE: The text file must be UTF-8 encoded and must contain a placeholder, called $ActiveMailAttachment$, that the SSDM replaces with the Active Mail NSF attachment when the message is migrated. Since the content of this file becomes part of an RTF body, characters such as "\", "{", and "}" must be escaped with a leading "\" (so they become, respectively, "\\", "\{", and "\}"). |
|
• |
[Notes] ActiveMailAttachmentName=<string> String; default = ActiveMail.nsf Specifies the filename you want MNE to assign to Active Mail attachment files as it will appear in the Outlook message. |
|
• |
[Notes] ActiveMailTypes=<#> Integer; default = 31 Specifies which types of Active Mail will be processed. The value is the sum of the associated values of these individual types: |
Configure data destinations for different data types
In the SSDM, the destination within Exchange of migrated data is not selectable in the GUI, but is controlled by three parameters in the [General] section of the notesdtapp.ini file. MNE lets you specify a migration destination within Exchange or Office 365 for each of the three primary data types to be migrated: archives, address books, and server-based data. Each type can be migrated to: user server-mail mailboxes, to user pst files, or to personal-archive (server-based) mailboxes.
Each parameter determines the destination of a particular data type (archives, PABs, or server mail), to be sent to the user server mail or to a pst file.
Option to migrate encrypted messages to PSTs
The SSDM can optionally direct encrypted messages to a separate PST file, no matter how many source.nsf files are selected for the migration. The feature is enabled/disabled by a notesdtapp.ini parameter that also specifies the full filename and extension for the target PST file:
In any subsequent SSDM runs, the program preserves the earlier PST files and automatically appends a digit to the designated filename to differentiate it from previously migrated PST files (filename.pst, filename_1.pst, filename_2.pst, etc.).
This feature is enabled only when all migrated items are directed to PST files by:
If any of the item types are directed to a non-PST destination, the EncryptedPstFileSuffix parameter is ignored.
Option to track unmigrated messages
The WriteFailedMessageListToThisMbxFolder parameter specifies a name for the folder to be added to the user mailbox to contain the unmigrated messages. WriteFailedMessageListClass specifies one or more types of message failures for the feature to capture. Valid keyword values are: Errored, Skipped and Filtered.
The example tells the SSDM to create copies of any Errored, Skipped and/or Filtered messages and save them in a new folder named FailedMessages in the user mailbox.
You enable this feature by entering any value for the WriteFailedMessageListToThisMbxFolder parameter. (If that parameter is omitted or its value is left empty, the feature is disabled and the WriteFailedMessageListClass parameter is ignored.) The feature is disabled by default (WriteFailedMessageListToThisMbxFolder is omitted or its value is [null]), and by default WriteFailedMessageListClass=Errored (only).