| Table of Contents |
|---|
In some circumstances it is possible that JEMHC has been configured to reject an incoming email, this could be via a global setting such as the issue comment limit, or via a project mapping setting such as the processing mode. JEMHC has the option to notify the sender of the email that their message has been rejected with a message rejection notification, this can be configured within a project mapping.
...
Message rejection configuration can be located within the Pre-Processing section of a Project Mapping, configuration will be inherited from the default Project Mapping if it is not overridden.
...
Configure a Template Set for message rejection notifications:
The template set that is used to generate message rejection notifications can be configured via Project Mapping → Templates → Message Rejected Template Set:
...
Configure message rejection notifications:
...
An example configuration to reject messages in the "Resolved" status:
...
The above configuration will result in a message rejection when an incoming email attempts to comment on an in issue that is in the defined status. The sender of the email will be notified of the message rejection via an email that will be generated using the project mapping defined message rejection template set. The end user will receive a rejection email similar to the following:
...
Configure message rejection notification when issue comment limit has been reached:
...
An issue comment limit can be defined within a profile, this limit will be apply to all Project Mappings within the associated profile. For example you could limit issues to a maximum of 1 comment. Any comments via JEMHC that are attempted on the issue after the comment count has reached the defined maximum will be rejected.
...
Enable rejection notification for issue comment limit:
A rejection message can be sent to the sender of the email by setting the "Notify Sender On Comment Limit Exceeded" field to "Yes" within the message rejection section of pre-processing:
...
The above configuration will results in a rejection message being sent to the email sender when a comment on an issue has been rejected due to the issue comment limit being reached:
...
Configure message rejection for issues that have been in resolved status for X days:
...
Configuration to disable comments on issues that have been in resolved status for more than 1 day:
...
Rejection notification received by the sender of the rejected comment email:
...
Configure message rejection notification when processing mode is comment only:
...
Configuration to enable a rejection notification when issue comment fails and processing mode is comment only:
...
Rejection notification received by the sender of the rejected email:
...
Configure message rejection notification when email comment is rejected because sender does not have permission to comment:
...
Configuration to enable a message rejection notification when issue comment fails because user does not have permission to comment:
...
Rejection notification received by the sender of the rejected email:
...
Message rejection based on JQL match
Similar to JEMH Server/DC, the ability to reject a message based on the JQL match allows expanded rejection criteria, as opposed to simply rejecting based on Issue Status.
| Info | ||||||||
|---|---|---|---|---|---|---|---|---|
This feature is currently in Development - Please see
|
New Issue creation during Message rejection match
Similar to JEMH Server/DC, this setting provides the ability to select whether messages are rejected (notifying using the rejection template), or if new Issues can be created if there is a message rejection match.
| Info | ||||||||
|---|---|---|---|---|---|---|---|---|
This feature is currently in Development - Please see
|