hold

Pending follow up from a user to create a related user account.

FILTERED

JEMH should not process the message and was processing was stopped on purpose due to filters i.e. Catch Email Address filter, Blocklisting

STOPPED

JEMH should not process the message and was processing was stopped on purpose due to something other than filters. I.e inhibition through scripting

NOT_PROCESSED

JEMH was prevented from processing further i.e. a Server Exception

PROCESSED

JEMH processed the message ( all filters have passed )

RE_PROCESSED

JEMH event was re-processed

RUNNING

JEMH is in processing the incoming mail.

Data_loss (Since 4.1.51 and 4.2.10)

There was an exception when processing an attachment and this has meant that the attachment was not added to the issue. More info about the exception can be found within the Report.

UNKNOWN

Either:

• the incoming mail process has just begun

• An unknown status occurred i.e. null status (this is a bug)

Blocked

• JEMH cannot process the mail i.e. there is a blocking condition(s):

  • JEMH is diasbled

  • Incoming Mail Message is null during processing ( i.e retrieval problem)

  • Jira Storage Issues:

    • Low disk space: Jira has less than 250MB available to store audit events

    • Jira Process User lacks write permission: <JIRA HOME>/jemh/data is not writable by the process user

DELETED

• Notification Summary Filter match

DROPPED

• Can be triggered by Profile level Filter handling i.e. Precedence Bulk Filter.

• Can be triggered by Profile level Allowlist Handling

• Can be triggered manually through scripting

FOLDER_CLOSED

• An IMAP folder closed during mail retrieval. Please see: Why do FolderClosedException occur | JEMH

FORWARDED

Sends a Forward notification to the 'forward' address, and delete the message from the mailbox

• Can be triggered by Profile level Filter handling i.e. Precedence Bulk Filter.

• Project Permission failure during processing i.e. User does not have commenting permission

• Can be triggered by Profile level Allowlist Handling

• Can be triggered manually through scripting

• When rejecting and HintOgram is not enabled then a forward will used instead

• Commit Limit handling

• Internal Error occuring during:

  • Issue creation

  • Issue update

  • Profile Retrieval

hold

• Requires further reprocessing to re-process the content once a user account has been added

IGNORED

• Global Blocklisting match

• Can be triggered by Profile level Allowlist Handling

• Can be triggered by Profile level Filter handling i.e. Precedence Bulk Filter.

• Can be triggered manually through scripting

INTERNAL_ERROR

• An Exception during processing

• No issue(s) was updated/created/commented

REJECTED

Send a reject Hint Notification to the sender and delete the message from the mailbox. More info here: JEMH Hint Notifications

• Can be triggered by Profile level Filter handling i.e. Precedence Bulk Filter.

• Can be triggered manually through scripting

• Thread match reject match

• Commit Limit handling

• Unable to find matching issue via directives/summary/subject

• User type permission i.e. if Non-Jira tries to create an issue via Jira user restricted profile

• If a valid Project Mapping is found:

  • No Project match was during incoming mail processing (this is to stop admin mailboxes from being spammed).

  • Comment Visibility permission failure

  • Comment creation processing failure

• From Address was not found incoming mail

• Worklog processing exception

• Nagios Field Map Extraction exception

• XML Field Map exctraction exception

• Reporter failed create/update/comment on an Issue

REMOVED

• JEMH Audit file could not be created as the message was removed from the mail server before it could be read fully (javax.mail.javax.mail.MessageRemovedException)

RUNNING

• Event is still being processed

SUCCESS

• Derived from CAN_HANDLE no issues detected during processing

UNKNOWN

Either:

• The incoming mail process has just begun

• An unknown outcome occurred i.e. null outcome (this is a bug)