These parameters are specifically for importing emails from mailboxes on Microsoft Exchange servers, that is, import operations of type EXCH (see Import.Type). They cover such areas as the names of the Exchange server and mailboxes you want to import from, the MAPI folders that you want to import, and whether the source emails are deleted after a successful import. There is also a ‘continuous import’ parameter that causes Event Import to repeatedly scan the target mailboxes for emails to be imported.
Note: See the 'MAPI Client and CDO 1.2.1' and mailbox requirements for EXCH import operations in Exchange and Outlook import operations.
Specifies the name of the Exchange server with the mailboxes you want to import. The syntax is:
MSExch.ServerName
Note: For Exchange Server 2013, this value must be entered in the guid@domain format. For example, set this value as F5FA2827-5978-43cd-8FA8-E07BC3BB5591@contoso.com.
Specifies the fully qualified domain name (FQDN) for a specific computer, or host, on the Internet.
Set this value to the standard FQDN. You need to specify http:// or https:// while setting this value. This is a mandatory setting and must be configured for Exchange 2013 only.
For example, set this value as https://e2013cas.contoso.com.
Specifies the authentication type to be used at the RPC/TCP layer.
Set this value to configure the authentication type. This setting must be configured for Exchange 2013 only. The following values are supported:
NEGOTIATE
WINNT
NONE
Specifies the authentication type to be used at the RPC/HTTP layer.
Set this value to configure the authentication type to be used at the RPC/HTTP layer. This setting must be configured for Exchange 2013 only. The following values are supported:
NEGOTIATE
NTLM
Provide the expected principal name of the server in Microsoft Standard format for a client. This configuration helps create mutually authenticated session with Exchange Server.
For example, set this value as msstd:e2013cas.contoso.com.
Specifies the name of the Exchange mailbox(es) you want to import. The syntax is:
MSExch.MailboxName=<mailbox>
You must supply the full Exchange mailbox name unless the last CN= component is known to be unique. If this is so, you need only specify this last component value to identify the mailbox. For example, for an Exchange address of:
/O=UNIPRAXIS/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=SRIMMEL
The command MSExch.MailboxName=SRIMMEL is sufficient for the Exchange server to resolve the address and identify the mailbox.
A single ‘Event Import’ import operation can include multiple instances of this parameter, each specifying a separate mailbox. All the mailboxes must reside on the same Exchange server. For example, to import the mailboxes for two users you add two lines to the import configuration file:
MSExch.MailboxName=SRIMMEL MSExch.MailboxName=FSCHAEFFER
Defaults to No. Specifies whether to delete the source emails (in the specified mailbox folders) after an import operation. The syntax is:
MSExch.DeleteEMailAfterImport=Yes, No or Always
If set to:
The source emails are never deleted. But be aware that if MSExch.FailedMailboxFolder is specified, then emails that fail to be imported will still be moved to the ‘failure’ folder.
The source emails are only deleted after a successful import operation.
The source emails are always deleted, whether the import succeeds or not.
Defaults to No. Specifies whether Event Import repeatedly scans the mailboxes specified by MSExch.MailboxName, and whether it shuts down after the mailboxes have been processed. The syntax is:
MSExch.ContinuousInput=No or Yes,<timeout in seconds>
If MSExch.ContinuousInput=Yes,<timeout> then Event Import waits after importing all emails from the specified mailboxes until the specified timeout expires. It then restarts the import operation. For example:
MSExch.ContinuousInput=Yes,20
Restarts import operations after 20 seconds. If no <timeout> is specified, Event Import waits 10 seconds before restarting.
Note: When importing from a mailbox (for example, for Import Policy), you need to set MSExch.DeleteEMailAfterImport=Yes, unless you are importing for diagnostic or testing purposes.
Specifies which MAPI folders within the mailbox to import. The syntax is:
MSExch.IncludeMailboxFolder=<folder_name>,Yes or No
If this parameter is not included, the entire contents of the mailbox are imported.
When identifying a folder, use backslashes as separators, followed by Yes or No to indicate whether subfolders are also imported. You must include a comma before the Yes or No option. If you do not specify Yes or No, you do not need a comma and MSExch.IncludeMailboxFolder defaults to Yes. The following examples illustrate the parameter usage:
MSExch.IncludeMailboxFolder="\Sent items",yes
Yes and No options are caseinsensitive.
MSExch.IncludeMailboxFolder=\inbox\UNIPRAXIS
Subfolders are imported automatically..
MSExch.IncludeMailboxFolder=\inbox\UNIPRAXIS,no
Subfolders are not imported.
A single ‘Event Import’ import operation can include multiple instances of this parameter, with each instance specifying a particular folder. For example, to import two mailbox folders you add two lines to the import configuration file:
MSExch.IncludeMailboxFolder=\inbox\Unipraxis MSExch.IncludeMailboxFolder="\inbox\Personal mail"
Note: If the folder does not exist within the source mailbox, an error is written to the Event Import log file. Find this in the \system\data\log subfolder in the CA Data Protection installation folder.
Specifies the name and path of a MAPI folder used to store emails that could not be imported. The syntax is:
MSExch.FailedMailboxFolder=<folder name>,Yes or No
This ‘failure’ folder is created as a subfolder below the user’s Exchange mailbox. When identifying a folder, use backslashes as separators, followed by Yes or No. If followed by:
The ‘failure’ folder is created automatically if it does not already exist.
The import job stops and an error is written to the Event Import log file.
You must include a comma before the Yes or No option. If you do not specify Yes or No, you do not need a comma and MSExch.FailedMailboxFolder defaults to Yes. The following examples illustrate the parameter usage:
MSExch.FailedMailboxFolder=\Failed,no
Yes and No options are case-insensitive.
MSExch.FailedMailboxFolder=\inbox\Failed
Subfolders are created automatically..
MSExch.FailedMailboxFolder="\Failed to import"
Enclose folder paths in double quotes if they include spaces.
Note: If MSExch.DeleteEMailAfterImport=Always, then emails that cannot not be imported are always deleted; they are not moved to a ‘failure’ folder.
Specifies a COM class name or GUID that contains an interface to a third-party archive system. The syntax is:
MSExch.ArchiveConnectorName=<Connector GUID or COM class>
The parameter enables emails imported from Exchange mailboxes to be physically stored as MAPI messages in a third-party archive system. CA Data Protection stores RDM references to the archived emails.
The required COM class name file or GUID depends on the archive system. For further details, please contact CA Support.
Defaults to No. Specifies how Event Import handles emails sent to distribution lists. The syntax is:
MSExch.ExpandDLs=Yes or No,[optional expansion limit]
Specifically, import jobs can be optionally amended to save distribution list members as event participants. This permits reviewers to search for any emails received by an internal user, not just emails where the user was specified as an individual addressee. If this parameter is set to:
Event Import does not expand distribution lists.
Instead, it handles the distribution list as though it were a single recipient, saving the distribution list itself as an ‘event participant’ and also saving the distribution list’s email address.
Unfortunately, this means you cannot search for these imported emails in the iConsole or Data Management console by specifying an individual recipient. Of course, because the sender is generally identifiable, you can still retrieve this imported email by searching for outgoing emails associated with the sender.
Event Import always expands distribution lists and creates separate participants for individual list members. By default, there is no limit on the number of individual recipients that Event Import can extract from a distribution list. For example, if a distribution list contains several nested distribution lists, Event Import extracts all members of the nested lists.
Delays can occur while the members are extracted and saved as event participants If the email was sent to a very large or heavily nested distribution list.
To alleviate this problem, you can specify an expansion limit. This causes Event Import to only expand distribution lists up to this specified limit. For example, to specify a maximum limit of 100 list members, set this parameter to:
MSExch.ExpandDLs=Yes,100
In this example, Event Import only creates separate participants for the first 100 list members.
Important! If a distribution list contains more than 100 members, any subsequent list members are not saved as participants!
Defaults to No. Specifies whether MAPI ignores the lack of a Public Folder store on the Exchange server. The syntax is:
MSExch.IgnoreNoPublicFolders=Yes or No
Specifies that MAPI fails to connect to the Exchange server if there is no Public Folder store. Choose No when attaching to an Exchange 2003 server.
Specifies that MAPI ignores the lack of a Public Folder store on the Exchange server. Choose this when attaching to an Exchange 2007 (or later) server where the Public Folder store is not deployed. Do not set this option to Yes when attaching to an Exchange 2003 server.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|