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:
split, email
Properties:
In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values.
| Name | Default Value | Allowable Values | Description |
| Additional Header List | x-mailer | 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. |
Relationships:
| Name | Description |
| success | Extraction was successful |
| failure | Flowfiles that could not be parsed as a RFC-2822 compliant message |
Reads Attributes:
None specified.
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 |
State management:
This component does not store state.
Restricted:
This component is not restricted.
How to configure?
Step 1: Drag and drop the ExtractEmailHeaders processor to canvas.
Step 2: Double click the processor to configure, the configuration dialog will be opened as follows,
Step 3: Check usage of each property and update those values.
Properties and usage:
Additional Header List: Enters the list of colon separated headers to be extracted from flow file content.
Email address parsing: Specifies which type of address format parsing rules should be followed.
- Strict Address Parsing
- Non-Strict Address Parsing
For example, to get x-mailer header from the received mails, you should follow the given configuration.
