Extensions

1 Summary
2 API’s
3 Message Filters
4 Attachment Filters
5 Alternate ID providers
6 Custom Field Adapters
7 Transport Providers
8 Field Processors
9 Mail Header Pre-Processing Tasks
10 Detected Script Engines

Summary

This screen shows the components that makeup the pluggable functionality of JEMH. Additional extensions can be deployed that integrate with JEMH. For some additional info see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/208142374

See the following page for API examples and information on how to use these APIs to create additional functionality: https://bitbucket.org/pluginpeople-public/jemh-example-extensions/src/master/

API’s

This shows what API extensions are available to JEMH and if they have been installed.

Message Filters

Message Filters are used to pick out problematic email's, before complex processing begins, allowing up front weeding out of broken emails (eg no From: address, no addressee). Filters can choose one of several predefined outcomes (canHandle, filtered, forward, reject, drop, delete), as well as providing reason text to support the decision, to be stored in the audit event.

Below is an example of the Message Filters that already comes with JEMH. If you have installed any additional filters then they will be shown within this list within JEMH.

Attachment Filters

Attachment filters are used to exclude specific attachments based on custom requirements. These are enabled within the relevant profile.

Currently JEMH contains the following attachment filters.

Alternate ID providers

Alternate ID Providers allow a means to determine users generated ID, and related firstname/lastname/email details, to be used during account provisioning. Also useful to 'translate' remote sender addresses, that may actually relate to a pre-existing user under a different email (for example, MS Exchange and proxyAddresses).

Currently JEMH contains the following ID providers:

Custom Field Adapters

Custom Field adapters that allow 3rd party addons to provide custom field population.

Transport Providers

Transport providers offer means for JEMH to issue notifications, or to be driven through.

Currently JEMH only contains the following Transport Providers:

Field Processors

Field Processors take a Message object and extract useful content (fields) from it that JEMH uses to populate an Issue.

This is where all of the available Field Processors are listed. This includes all Custom field Processors that have been added. For more info about Custom Field Processors see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/32047288

Mail Header Pre-Processing Tasks

Mail Header Pre-Processing Tasks allow low level manipulation of an Email's Headers prior to processing by JEMH. This is where all of the available Pre-Processing Tasks are listed:

Detected Script Engines

Here we list the detected ScriptEngines that JEMH could use. See Install a Scripting runtime Engine (Nashorn, Groovy, Graal) for help on how to install more runtime engines.