Specifications

DescriptionProperty
Defines the "key" that is used to select the appropriate email
info from the table provided in the next property; the key can
Base map key on
be contents of: “Sender’s email address”, “Email account
name”, or “Message subject”
Email addresses and body text specified with the editor for this
property are added to each file's email info as the file is injected
Email info map
in the flow; the value of the key specified in the previous
property (for example, the sender's address of the incoming
email message) determines which entry of the table is actually
added
When set to "Yes", user can scan all nested email until no emails
but real assets are found. By default, "No" is selected in this
menu
Scan for nested attachments
Set to "Yes" to collect all attachments in a folder. Single file
attachments will also be stored in a job folder. By default, "No"
is selected in this menu
Collect attachments
This is a sub property of Collect attachments and is available
only when the parent is set to yes. Set to "Yes" to assemble the
Assemble message and
attachments
injected message and the attachment(s) in the same job folder.
If there is no message to inject, this property will not affect
attachment handling. By default, "No" is selected in this menu
Determines whether the email message itself (as opposed to its
attachments) is injected into the flow as a separate file; choices
are:
Inject message as file
• No: only attachments are injected in the flow
• If no attachments: the mail message is injected as a separate
file only if it has no attachments
• Always: the mail message is always injected as a separate
file
The message body is converted to plain text and saved into a
“.txt” file with UTF8 encoding and named for the subject line
of the email message. However, if the email message does not
have a subject line, it is saved into a file named "No
subject.txt".
Picking up email metadata
The mail receive tool automatically picks up the contents of incoming email messages as metadata.
This behavior cannot be configured or turned off (that is, there are no flow element properties
related to this behavior). See Picking up metadata on page 315 for more background information.
For each incoming message the mail receive tool creates a metadata dataset that contains the
relevant components of the message, such as the sender, to, cc, and reply-to addresses and the
complete email body text. This dataset is then associated with the job ticket for all files delivered
by the message under the standard dataset name “Email”.
266
Enfocus Switch 10