Tasks available vary by JEMH version

Pre-processing tasks are designed to help overcome specific problems that emails can have.  It is strongly recommended that a task is not enabled unless you are certain of the cause of a processing problem.

Function

If the To: header is missing (perhaps because the message was BCC delivered and the final leg mail host didn't include a courteous Delivered-To: header, then JEMH can inject a configurable value. By missing, it could also be the case that the To: header is present without a value.

Scenario

In this case, clicking the edit icon brings up the editable address entry form. A single valid SMTP address should be supplied, that can include personal part if needed, eg:

• user@place.com

• <user@place.com>

• "Personal Part" <user@place.com>

Here is what it looks like after selecting during editing the Email section:

Clicking the pen icon above allows entry of the address:

Function

Fixes various problems that can occur with Groupwise addressees.

Scenario

In this case, clicking the edit icon brings up the properties dialog for the task:

In this case, the options have been set to manipulate the nominated Groupwise Group (which did not expand to addressees, and therefore made the message unreadable), converting spaces to underscores, and embedding the result in the %group% renamed address.  The result of this is that When a group 'Some Whitelisted Groupname' is encountered, it is replaced with the valid email address <Some_Whitelisted_Groupname@yourco.net>, enabling the message to be processed - automatically!

Group Handling

• Remove (all groups) such that only email addresses remain.

• Rename (some or all groups) to email addresses using the remaining fields.

Group Whitelisting

If specified, lists (comma separated) the actual group names listed in the Email addressee fields that should be renamed to email addresses.  Leaving this field empty means that all Groups will be converted.

Space Replacement Char

Removing the spaces in the group enables (test cases to date)  a valid email addressee to be formed, default is an underscore.  Only the first character of a supplied value is used.

Rename Pattern

The given pattern %group%@yourco.net allows the group above, to be injected into this template, so that addresses are formed.

Illegal Main content CharType

Maps top level email header MIME content types that are invalid for Java Mail, to ones that are valid (see https://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html )

Scenario

Lets say you wish to process the following email:

Subject: TEST
To: changeme@thiswontwork.com
From: sender@example.com
Date: Wed, 13 Nov 2015 11:22:11 +0900
MIME-Version: 1.0
Content-type: text/plain; charset=GB2312
Content-transfer-encoding: base64

<encoded content>

Charset GB2312 is not valid for Java Mail to process.  Therefore, when the mail is processed, you may find some characters are not shown properly.  In order to get around this we will map to the similar but valid GBK charset.

Configuration

• Select the task from the list of tasks and save

• Click Edit on the task

• Enter the mapping that you would like to make

Mappings for Known Problem Content Types

The following is a list of known configurations for problem content types.

Function

This pre-proc task can also update Mime Multipart encoded mail to correct illegal/incorrect mime types, eg, in the following, the Sender declares the content type of the attachment within to ‘uknown/pdf’, which in itself causes no problem, however, when downloading, client Browsers don’t know how to handle that, and cannot associate with the PDF client reader app.

From: <sender@blah.com>
Subject: stuff
To: <c@d.com>
CC: <a@b.com>
Date: Fri, 27 Aug 2021 05:15:17 +0200
Message-ID: <OF15486DFF.F74916F2-ONC125873E.0011E105@nnnnn.com>
Content-Type: multipart/mixed;
	boundary="PART.BOUNDARY.MU.123.456.789"
MIME-Version: 1.0

--PART.BOUNDARY.MU.123.456.789
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="borked"

payload here

--PART.BOUNDARY.MU.123.456.789
Content-Type: unknown/pdf; name="FBB BE.PDF"
Content-Disposition: attachment; filename="FBB BE.PDF"
Content-Transfer-Encoding: base64

encoded content here

--PART.BOUNDARY.MU.123.456.789--

This can then be corrected with:

unknown/pdf=application/pdf

Function

Allows illegal/redundant content-encoding value (e.g. UTF-8) present in the Content-Transfer-Encoding header to be removed or replaced with another value.

The below example caters to a specific issue where an email has the Content-Transfer-Encoding header defined with a value of UTF-8, this is an invalid content encoding type and will cause email processing to fail.

The pre-processing task can be configured with a key=value replacement for invalid content transfer encoding values, in the screenshot below the content transfer value UTF-8 has been substituted for an empty value by specifying UTF-8= in the pre-processing task configuration.

Configuration

Function

Allows illegal MIME multipart boundaries to be fixed dynamically.

Configuration

No configurable properties are available for this pre-processing task.

Function

Filter the "From", "To" and "Cc" addresses for illegal quoting of addresses.

Scenario

JEMH may encounter an incoming email with illegal quotes in an address field, for example:

To: "Bob Bobbington" <'bob@bob.com'>

The Quoted Address Removal task can fix this field in order to allow successful processing:

To: "Bob Bobbington" <bob@bob.com>

Configuration

No configurable properties are available for this pre-processing task.

Function

Filter From, To and Cc addresses for illegal single leading quoting personal names.

Scenario

JEMH may encounter an incoming email that does not correctly quote the personal name of an address:

" <some@place.com>

This pre-processing task can fix this problem in order for processing to be successful:

<some@place.com>

Configuration

No configurable properties are available for this pre-processing task.

Function

Filter the "From", "To" and "Cc" addresses for illegal trailing dot.

Scenario

JEMH may encounter an incoming email with trailing dots in an address field, for example:

From: "Bob Bobbington" <bob@bob.com.>

The Trailing Dot Address Removal task can "fix" this field:

From: "Bob Bobbington" <bob@bob.com>

Configuration

No configurable properties are available for this pre-processing task.

Function

Filter the "From", "To" and "Cc" addresses for illegal double address routes.

Scenario

JEMH may encounter an incoming email with double address routes in an address field, for example:

From: <bob@bob.com> <bob@bob.com>

This can be fixed:

From: "bob@bob.com" <bob@bob.com>

Configuration

No configurable properties are available for this pre-processing task.

Function

Filter body content for Content Disposition multi-parts that are non-compliant and not parseable (spaces in file names that are not quoted).

Scenario

When attachments are present in a multi-part email, JEMH may encounter file names that contain spaces that are unquoted.

Configuration

No configurable properties are available for this pre-processing task.

Function

Allows messages without a From: address to be dynamically updated for a given address

Scenario

In some cases, JEMH may encounter a mail which does not have the From address specified.

Configuration

The DefaultAddress to be used if the From Address is not specified is configurable; but do ensure that a valid email address is used (x@y.com) format

Function

Allows messages with missing Content-Disposition attribute to be defaulted to Content-Disposition: attachment

Scenario

In some cases, if the mail server fails to successfully specify the Content Type of an attachment (if it should be inline, attached and so on), this ends up throwing an error in JEMH as JEMH fails to successfully parse the mail. Therefore, it's important to ensure that the content type of an attachment is specified accordingly to ensure successful parsing phase.

Configuration

No configurable properties are available for this pre-processing task and if Content Type is invalid/not specified - default value (Attachment) will be inject. 

Function

Allows the user to specify the a specific header and value in order to determine if the mail is a spam mail (potentially generated by an Automated Service/s)

Scenario

Automated systems may send out numerous emails which are not easy to identify as a spam email and don't always contain the corresponding spam header. With this task, you can specify the Header and the Header value in which JEMH will perform a validation against to check the existence of that Header and Header Value. If found, Spam flag will be injected in which you can configure the Email section of the Project Mapping to process as per configuration. 

Configuration

Following values are configurable:

• Spam Header - the header value which will be used to perform the search against

• Spam Header Value - the value which the header (configured against Spam Header) contains

Do note that a case insensitive search is performed against the contents for both of the values.

Function

Filters From, To and Cc/Bcc addresses for only local email addresses (missing @domain) and removes them. There are no configuration options for this Task.

Scenario

Automated system is sending out emails that only contains the first part of email (the name section e.g.bob instead of bob@localhost.com) and as a result it causing issues with processing these emails. With this task, it will detect whether any of the email addresses within From, To and Cc/Bcc do not contain the domain part of the email address (@localhost)

Configuration

There is no Configuration options for this task.

Function

Remove any singles quotes that are found within the Content-Type value. e.g. Content-Type: text/plain; charset='utf-8'.

Scenario

Sometimes JEMH may enter a email that contains Single Quotes around the charset value. Which will cause the email to not be processed correctly. This task will remove the Single Quotes so that JEMH is able to process the email with no issues. e.g. Changing From (Content-Type: text/plain; charset='utf-8') to (Content-Type: text/plain; charset=utf-8).

Configuration

There is no Configuration options for this task.

Function

Removes Semi-Colons from the To/Cc headers when they are used to separate recipients.

Scenario

JEMH receives an email that use a Semi-Colon to separate the recipients within the To/Cc headers. This task will remove the Semi-Colon and will replace this with a comma so that it uses the correct format. E.g. changes header from: user@domain.com;user2@domain.com to user@domain.com, user@domain.com

Configuration

There is no Configuration options for this task.

Function

Removes 4-byte characters from encoded email subjects which can cause failures when saving to MySQL databases.

Scenario

Jira is configured to save your data into a Mysql database and you are receiving emails that contain 4-byte characters within the subject which can cause issue when save into the database. This task will match and remove these 4-byte characters so that there is no issues with saving into Mysql.

Configuration

There is no Configuration options for this task.