Previous Topic: Set Up the Input Mailbox SubkeysNext Topic: Include and Exclude Filters


Templates Subkey

This subkey contains the following registry values:

Outputs

Type: REG_SZ

Data: Specifies a comma-separated list of the outputs that the Universal Adapter will output e‑mails to. For example, MailboxPool1 and MailboxPool2. This list must match the subkey names listed under the Output registry key.

Type

Type: REG_SZ

Data: Set this to Exch or Notes and specifies whether the mailbox uses Microsoft Exchange or Domino Server. All mailboxes must use the same type.

DeDuplicate

Type: REG_DWORD

Data: Defaults to 0. Set this to 1 or 0. If set to 1, the Universal Adapter will process e‑mails via the de‑duplication database. If set to 0, de-duplication is disabled.

Notes:

DeEnvelope

Type: REG_DWORD

Data: Defaults to 1. This Exchange-only value can be set to 1 or 0 and specifies whether de-enveloping is enabled. If set to 1, any e‑mails being imported that had previously been through the Microsoft Exchange envelope journaling process are de-enveloped.

Any emails in the mailbox that have not been through this process are simply imported in their current format. That is, they are not de-enveloped.

Note: This value applies to mailbox outputs only.

DuplicatesDatabase

Type: REG_SZ

Data: Specifies the name of the Domiono database used to store duplicate emails.

Note: This setting is provided for testing and diagnostic purposes.

Note: This setting is only applicable when processing emails in a Domino mailbox. If processing Exchange emails, use the DuplicatesMailboxFolder registry value.

DuplicatesMailboxFolder

Type: REG_SZ

Data: Specifies the name of the folder within the Exchange mailbox used to store duplicate emails. When identifying a folder, use backslashes as path separators. For example, \Duplicates will place all duplicate emails in a subfolder named Duplicates in the root of the mailbox. If this registry setting does not exist and de‑duplication is enabled, then duplicate emails will simply be deleted.

Note: This setting is provided for testing and diagnostic purposes.

Note: This setting is only applicable when processing emails in an Exchange mailbox. If processing Domino emails, use the DuplicatesDatabase registry value.

ExpandDLs

Type: REG_SZ

Data: Defaults to No. Applies to Universal Adapter outputs only. Set this to Yes or No to specify whether the UA will expand an e‑mail’s distribution lists before it is output. If set to Yes, you also need to specify a threshold number of list members. For example, to expand up to 20 members of a distribution list, set this registry value to Yes, 20.

Notes:

After expanding this number of recipients from the distribution list, or if the Universal Adapter detects that expanding a nested distribution list would exceed this number, no further individual recipients are extracted for that DL. Other remaining DLs may still be expanded.

Note: This ExpandDLs setting is ignored for envelope journaled emails as DLs have already been expanded by the Exchange servers.

FailedMailboxFolder

Type: REG_SZ

Data: Specifies the name of the folder within the mailbox used to store emails that the UA could not process. For example, this can happen if the content of the email is corrupted, or because the server hosting the output is unavailable. When identifying a folder, use backslashes as path separators. For example, \Failed will place all failed emails in a subfolder named Failed in the root of the mailbox.

FailBlockedMessages

Type: REG_DWORD

Data: Defaults to 0. If set to 1, moves any currently failing e‑mails directly to the \Failed folder, and does not try to reprocess them. This registry value returns to its default setting of 0 after any currently failing emails are moved to the \Failed folder.

Important! Setting this registry value has no affect on future failing emails. It only moves currently failing emails.

RetryFailedFolderMessages

Type: REG_DWORD

Data: Moves failed emails back to the Inbox so they can be re-processed.

ApplyPolicy

Type: REG_MULTI_SZ

Data: Defaults to No. This value can be set to Yes or No and specifies whether the UA connects to a policy engine (via a hub) to apply policy and generate smart tags for the emails being processed.

Note: The UA can only connect to a policy engine hub; it cannot connect directly to a policy engine.