...
The description of the selected Profile. Allows a more detailed description for other users to understand the purpose of the selected Profile.
Readiness
When making Profile changesIf you are managing multiple configuration profiles, you may not deem a Profile as ‘ready’ for your instancehave some that are not ready for use. The readiness setting allows you to filter the profile into the selected ‘readiness’ optioncategorize your profiles for organizational purposes. Available options are:
DevelopmentUATProduction
Catch Email Addresses
The specified emails and regex values will be used to find a catch email address matching the incoming emails recipients.
When JEMHC processes an incoming email is processed, there must be at least one recipient that matches the provided catch email address values. If a matching catch email address is not found, the email cannot be processed. (See ‘Non-catch Email Action’ to configure what should happen in this scenario).
...
Previously named Catch Email Headers. The provided CSV list of email header names will be used to check the incoming email headers for a matching catch email address value.If left empty, To, Cc and Bcc will be checkedBy default, the following email headers will be checked for recipient addresses and catch email addresses:
ToCcBccDelivered-ToNewsgroups
Here you can provide a comma-separated list of email header names to check in addition to the above.
Non-catch Email Action
If an incoming email does not match the catch email address values above, the following action will be taken.
...
Forward User Email Addresses
When email processing incoming email failures occur, JEMH Cloud will notify the forward user emails provided will be notified when the outcome operation is set to ‘Forward’ Forward.
| Info |
|---|
This address should not be a Incoming Mail Server Address as this would cause issues such as Mail Loops which you would not want to occur. |
Act As User Feature Enabled
When enabled, JEMH Cloud will attempt to perform comment operations on behalf of Jira users (meaning issue comment actions . This means that comments will have the specific Jira user marked set as the its author of the comment).
Rule Evaluation Strategy
...
When an incoming email subject is larger than the description field character limit, this setting changes how we handle the remaining content.
Clip and Attach - :
... remainder clipped, see originalwill be added to the description and the remaining content will be attached to the Issue.Cut remaining - : The maximum character limit will truncate the description content. Data will be lost if the description is larger than the maximum description character limit.
...
Any CSV values provided will be used to prevent incoming emails that contain a matching excluded recipient from being processed. For example, this can be used to prevent email processing of emails that were bulk sent to specific email addresses.
| Info |
|---|
How |
...
these exclusions are handled is set through Profile Exclusion Action (below) |
Excluded Subjects
Any CSV values provided will be used to prevent incoming emails that contain a matching excluded subject from being processed.
| Info |
|---|
How |
...
these exclusions are handled is set through Profile Exclusion Action (below) |
Profile Exclusion Action
When an incoming email matches against the above inclusion or exclusion rules, the selected action will be used on the incoming email.
...
Global Exclusion Action
This setting defines the behaviour behavior action for incoming emails when the global exclusion configuration is applied. (See Global Exclusions ).
...
When handling incoming emails that are Bounce emails, this setting determines the behaviour behavior action that should be applied.
...
When an incoming email processing error occurs, this setting defines the behaviour behavior action that should be applied. This setting is only for processing failures. Exclusion action and other processing configuration uses their configured values.
...
Forward Email Message Level Threshold
Only available when ‘Error Action’ Error Action is set to ‘Forward’ Forward.
The threshold level is used to know which threshold level of reports should send forward notifications. ( If the generated report matches is greater than or equal to the selected value or abovelevel, the notification is sent).
Possible actions options are:
SuccessInfoWarningError
For example, if a processing error occurs when the threshold is set to ‘error' Error, forward notifications will be sent out if the processing report is of ‘error’ Error type.
Precedence Bulk Action
...
Allow - Continue processing the incoming email.
Forward - A forward notification will be sent to the configured forward users (. See https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/3708944393/Profile+Configuration#Forward-User-Email-Addresses ) for more.
Drop - The incoming email will be dropped, processing stopped.
...
If left empty, all the emails with precedence bulk header are considered for Precedence Bulk Action.
Sender is Bulk
The numeric value If specified, this determines the number of emails a user can send every hour before messages are considered as ‘bulk messages’.
In the scenario another email is sent after reaching the configured limit, the precedence bulk action will be used. ( See https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/3708944393/Profile+Configuration#Precedence-Bulk-Action ) for more.
If left empty, this feature is disabled.
Drop Messages With Headers
...
Use Preprocessed Message
This Feature must be enabled to allow pre-processing tasks to be used
...
See also the Pre-Processing page for more information.
Quoted Address Removal
This will check whether any of the From, To and Cc addresses for any illegal quotes and will then remove any illegal quotes. e.g. "Some Name" <'some@place.com'>→ "Some Name" <some@place<some@place.com>com>
Double Route Address Removal
This will check whether any of the From, To and Cc addresses for illegal double addresses. If found it will quote the first address as a personal part. e.g. <some@place.com> <some@place.com> <some@place.com> <some@place.com> → "some@place.com" <some@place<some@place.com>com>.
Single Leading Quoted Personal Fixer
This will find and remove any illegal empty quotations. e.g. ' ' <some@place<some@place.com> com> → <some@place <some@place.com>
Trailing Dot Address Removal
This will find and remove any trailing dots that are found within the From, To and Cc addresses. e.g. "Some Name" <some@place.com.> → "Some Name" <some@place<some@place.com>
Unwrapped Email Address Fixer
This will find any unwrapped email addresses and will wrap them within “<“ and “>”. This will only be applied when a personal is provided. e.g. "Some Name" some@place.com → "Some Name" <some@place<some@place.com>com>
Missing Recipient Address Fixer
...
Illegal Disposition Fixer
Fixes broken/unknown Content-Disposition headers, setting up a configurable default header value will allow you to enter a default Content-Disposition to use. Recommended values are attachment or inline
...