ExtractEmailHeaders 2.3.0¶

BUNDLE¶

org.apache.nifi | nifi-email-nar

DESCRIPTION¶

Using the flowfile content as source of data, extract header from an RFC compliant email file adding the relevant attributes to the flowfile. This processor does not perform extensive RFC validation but still requires a bare minimum compliance with RFC 2822

TAGS¶

email, split

INPUT REQUIREMENT¶

REQUIRED

Supports Sensitive Dynamic Properties¶

false

PROPERTIES¶

Property	Description
CAPTURED_HEADERS	COLON separated list of additional headers to be extracted from the flowfile content.NOTE the header key is case insensitive and will be matched as lower-case. Values will respect email contents.
STRICT_ADDRESS_PARSING	If “strict”, strict address format parsing rules are applied to mailbox and mailbox list fields, such as “to” and “from” headers, and FlowFiles with poorly formed addresses will be routed to the failure relationship, similar to messages that fail RFC compliant format validation. If “non-strict”, the processor will extract the contents of mailbox list headers as comma-separated values without attempting to parse each value as well-formed Internet mailbox addresses. This is optional and defaults to Strict Address Parsing

Property

Description

CAPTURED_HEADERS

COLON separated list of additional headers to be extracted from the flowfile content.NOTE the header key is case insensitive and will be matched as lower-case. Values will respect email contents.

STRICT_ADDRESS_PARSING

If “strict”, strict address format parsing rules are applied to mailbox and mailbox list fields, such as “to” and “from” headers, and FlowFiles with poorly formed addresses will be routed to the failure relationship, similar to messages that fail RFC compliant format validation. If “non-strict”, the processor will extract the contents of mailbox list headers as comma-separated values without attempting to parse each value as well-formed Internet mailbox addresses. This is optional and defaults to Strict Address Parsing

RELATIONSHIPS¶

NAME	DESCRIPTION
failure	Flowfiles that could not be parsed as a RFC-2822 compliant message
success	Extraction was successful

WRITES ATTRIBUTES¶

NAME	DESCRIPTION
email.headers.bcc.*	Each individual BCC recipient (if available)
email.headers.cc.*	Each individual CC recipient (if available)
email.headers.from.*	Each individual mailbox contained in the From of the Email (array as per RFC-2822)
email.headers.message-id	The value of the Message-ID header (if available)
email.headers.received_date	The Received-Date of the message (if available)
email.headers.sent_date	Date the message was sent
email.headers.subject	Subject of the message (if available)
email.headers.to.*	Each individual TO recipient (if available)
email.attachment_count	Number of attachments of the message