...
This flavour of non-JIRA user has no account, does not require any special groups and not being interactive, does not contribute to seat count. Incoming mail is 'intercepted', email addresses are extracted and stored in standard JIRA custom fields. JEMH requires a 'proxy' default reporter to be defined, this is the user that the issue will be created 'as'. The address of this user should not be a valid incoming mailbox address, in fact this addressee can be blacklisted blocklisted within the JEMH Event Listener to stop any 'useless' notifications.
...