...
Current Options for all of the filters are either Disabled (Blank) or Enabled.
Filter name | Filter’s function |
---|---|
Valid Email Address filter | Ensures that any email coming in has a valid From: address, and that all recipients are also valid. |
CatchEmail Address filter | Checks the incoming email address matches a catchmail / jemhAddresseeRegexp value |
Status Notification Action filter | Intercepts mails that are a reply to a JEMH Summary Notification, processing summary for actions, eg when content is single word: Unsubscribe |
X-JIRA-FINGERPRINT filter | Filter to weed out mails with this servers X-JIRA-FINGERPRINT, resulting in forwarding |
Allowlisting/Blocklisting filter | Applies blocklisting/allowlisting, processing such mail as configured. |
User Signup filter | Handles Messages from users replying to user-creation confirmation requests |
X-Spam-Flag filter | Filter to weed out X-Spam-Flag mails |
Precedence: |
...
bulk |
...
/junk |
...
/list |
...
and Auto-submitted: |
...
auto-replied |
...
filter | Intercepts mails with a bulk/junk/list precedence, takes configured action if found |
Custom message filter | Allows Jira admins to define Custom Header and Header values that should result in the email be Dropped/Forwarded. Once enabled here, you will then be able to configure the Custom Header and Header values within Profile > Project Mapping > Email > Custom Message Filter Actions. For more info see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/3801939983/Email+Project+Mapping#Custom-Message-Filter-Actions---Since-4.1.21 |
Comment count rate limit filter | Checks the number of incoming messages for the certain period of time. This is a denial of service attack preventative and anti-email-loop measure |
Non-delivery filter | Intercepts non-delivery messages from mail servers and drops (failure in processing will result in a forward). This filter checks all message parts to see if they have a Content type of “multipart/report” with a Report type of “delivery-status”. This includes attachments as some Mail Server will contain the Non-Delivery report as an attachment so this ensures they cannot create new issues. |
Directive Set Reply filter |
...
...
colour | Red |
---|---|
title | SINCE 4.1.10 |
When an incoming email contains a Directive Set token within the Subject. The Subject would need to contain “JEMH_TOKEN=dc2344…” in order to match. For more info see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/114982925/Use+Directive+Sets#Process-email-using-Directive-Set-Message-Filter---Since-4.1.10 |
...
Custom filter -
Status | ||||
---|---|---|---|---|
|
Allows Jira admins to define Custom Header and Header values that should result in the email be Dropped/Forwarded.
...
For more info see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/3801939983/Email+Project+Mapping#Custom-Message-Filter-Actions---Since-4.1.21
Non JIRA account holder Security Check filter | A security filter that can reject emails from non-jira users, that refer to an existing issue where that sender is not already involved (added as a non-jira user to a TEXT custom field) |
Comment |
...
count limit filter | Checks incoming messages for specific limits, regarding size, and comment count on an issue. This is a denial of service attack preventative and anti-email-loop measure. |
Exchange Auto Response filter | Filters emails which contain both the X-Auto-Response-Suppress and X-MS-Exchange-Inbox-Rules-Loop headers |
Related Pages
Filter by label (Content by label) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|