Platform Deployment Guide › EML Conversion Utilities: Cnv2email and BB2email › Embedded Content Details Saved in EML x-headers › Configure Policy Engines to Detect Embedded Content Emails › Detect Other Embedded Content › Syntax for ‘Embedded Message Identification’ Policy Setting

Syntax for ‘Embedded Message Identification’ Policy Setting

If you want policy engines to detect other forms of embedded content in EML emails (such as eFaxes or IM conversations converted by third party applications), you must add additional values to the Embedded Message Identification policy setting, using this syntax:

<TYPE>:where "<X-header>" 
[IS or CONTAINS "<Header value>"]
[<IM action> "<Network>"]

where:

<TYPE>

Determines the event type. It can be IM or BB (for Bloomberg messages). In addition, this can be set to EFAX to detect eFaxes (see next section).

<X-header>

Is the name of the x-header that the policy engine must look for when processing the EML email. You must enclose the x-header name in double quotes.

IS or CONTAINS <Header value>

Validates the x‑header. These operators test whether the actual text value of the x‑header is, or contains, the text defined by <Header value>. You must enclose the text in double quotes.

Note: These operators are not needed to process ‘IM’ EML files generated by Cnv2email.exe. Policy engines can automatically detect the IM network embedded in these EML files.

<IM action>

Is only needed when processing ‘IM’ EML files. It can be either SetIMNetwork or ExtractIMNetwork.

<Network>

Is only needed when processing ‘IM’ EML files. If <IM action> is set to:

• SetIMNetwork, then <Network> specifies the IM network that you want to assign to the resulting ‘embedded IM’ event. You must enclose the IM network in double quotes.
• ExtractIMNetwork, then <Network> extracts the specified text from the x-header and saves this text as the IM network when generating an ‘embedded IM’ event. Note that you can use a conversion expression to modify this extracted text before storing the IM network. You must enclose the specified text or conversion expression in double quotes.

These conversion expressions use the same syntax as the conversion expressions for importing LDAP attributes. They can parse, extract and (if necessary) remove or substitute any characters in the IM network.

More information:

Conversion Expression Syntax