Page Comparison

...

First, JEMH's Auditing feature must be enabled. To do this, go to JEMH>Auditing>Auditing Enablement JEMH>Auditing>Settings>Inbound auditing and click Enablethe Toggle Switch. This is required as the Auditing function handles the storage of incoming emails.

...

Panel

Status

subtle	true
colour	Red
title	Since 1.7.x

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:

Image Modified

Clicking the pen icon above allows entry of the address:

Image Modified

Groupwise Addressee

Panel

Status

subtle	true
colour	Red
title	Since 1.5.x

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:

Image Modified

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.

...

Panel

Status

subtle	true
colour	Red
title	Since 1.6.x

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:

Code Block

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

Image Modified

Mappings for Known Problem Content Types

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

Problem Type	Description	Configuration
GB2312	GB2312 charset is not valid for Java Mail to process. Mapping to the similar GBK charset makes it work.	GB2312=GBK
CP932	CP932 is Microsoft's extension of the Shift_JIS character encoding. Java Mail does not recognise this as an alias. MS932 is a supported alias.	CP932=MS932

Panel

Mime Multipart

Status

colour	Green
title	since 3.3.52

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.

Code Block

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:

Code Block
unknown/pdf=application/pdf

...

Panel

Status

subtle	true
colour	Red
title	Since 1.7.x

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

Image Modified

Email header before pre-processing task	Email header after pre-processing task
Content-Transfer-Encoding: UTF-8	Content-Transfer-Encoding:

MIME Multipart Boundary Updater

...

Panel

Status

subtle	true
colour	Red
title	SINCE 3.0.19

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

Image Modified

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

...

Panel

Status

subtle	true
colour	Red
title	SINCE 3.1.5

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

Image Modified

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.

...

Versions Compared

Old Version 13

New Version 14

Key

Function

Scenario

Groupwise Addressee

Function

Scenario

Group Handling

Group Whitelisting

Space Replacement Char

Rename Pattern

Illegal Main content CharType

Scenario

Configuration

Mappings for Known Problem Content Types

Mime Multipart

Function

Configuration

MIME Multipart Boundary Updater

Function

Scenario

Configuration

Function

Scenario

Configuration