Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Summary

Here you define what should happen to emails that contains specific headers.

Message Filter Actions

This defines what should happen when a email contains the following headers.

  1. Precedence: Bulk

  2. Precedence: Junk

  3. Precedence: List

  4. X-SPAM-Flag

  5. X-JIRA-Fingerprint

The current options are:

  1. Drop (exit group) - Drops the email and stops any further processing and does not check any other Profiles (Only applies to Profile Groups)

  2. Drop - Drops the email and stops any further processing

  3. Allow - Allows emails with the header to create/comment on issues.

  4. Forward - Stops processing and will send a Forward notification to the Forward Users defined within Profile > Notifications.

Custom Message Filter Actions - SINCE 4.1.21

You may need to enable Profile > Message Filters > Custom message filter to be able to use this feature. For more info see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/3782049801/Message+Filters#Custom-filter---since-4.1.21

Allows you to specify Custom Headers and Header Values that can be matched to stop emails from processing further. These are Comma Separated Values which means that multiple headers and values can be defined for each outcome.

Matching header with a specific value.

To match a header with a specific value you would need to specify the header and the value using the following format. If this header is found with that value then the email will be Dropped or Forwarded

Header2: headerValue2

Configuration options

Custom: Forward

If one of the defined headers is found in the email then it will result in a forward notification being sent to the forward users and there will be no further processing of the email.

Custom: Drop

If one of the defined headers is found in the email then it will result in a Drop outcome and no further processing will occur and no notification will be sent to forward users.

If using Profile Group then it will mean that the next Profile will be checked for processing.

Custom: Drop (exit group)

If one of the defined headers is found in the email then it will result in a Drop (exit group) outcome, which means no further processing will occur (even if using a Profile group) and no notification will be sent.

Archived issue handling

This is where you configure how JEMH will handle commenting on an issue that has been archived. The current options are:

  1. Forward - Sends a Forward notification to the Forward Users defined within Profile > Notifications.

  2. Reject - Rejects the email and will send a Reject notification to the sender if Hint notifications are enabled.

Related Pages

  • No labels