Page Comparison

...

• An active Jira Cloud instance that you have administration rights for

• For inbound email processing:

  • A valid Jira project

  • An external (non-Atlassian) mail source, for example a POP or IMAP server visible by JEMHC - Setup JEMHC Inbound mail (typically through a cloud provider like O365, Gmail, but could be your own).

• For outbound email notification:

  • An external (non-Atlassian) SMTP mail server.

...

Setup inbound mail processing

...

You will likely need to whitelist the JEMHC application IP address for access to your mailservers:

• JEMHC Public IP Address : 54.210.55.45

Be aware that this access is for our system, as such, it is technically possible for your mailserver to be contacted by other users of JEMHC - for this reason, we do not recommend/support pass-wordless mail servers!

Next we will configure JEMHC to process emails retrieved from an incoming mail server. Firstly, we will select our first project that emails should create issues in. Do not worry, later on you can add additional projects to the configuration - this is just for initial set up. You will also be asked for an issue type.

...

Expand
title Create Message Source configuration assistance
Setting Description Name Name of the message source Type Message source type Preset Presets which can be used to simplify the remaining configuration i.e. Host/Post Host Message Server's hostname or IP Address Port Message Server's port Timeout Connection to be timed out based on the configured time (seconds). Leaving this configuration blank would result the timeout to be 30 second Username Username to access the account Password Password to access the account SSL Does the connection use SSL? SSL Certificate Validation SSL Certification Validation Check Server Identity RFC 2595 specifies additional checks that must be performed on the server's certificate to ensure that the server you connected to is the server you intended to connect to. This reduces the risk of 'man in the middle' attacks. Read Strategy Read Unread and Mark As Read - Only the unread emails in the mailbox are to be processed and once read, they will be flagged as read (Default).  Read All and Delete - All the emails in the mailbox will be read and deleted after they are successfully processed. NOTE: You should be fully aware of the changes you make when switching between strategies as it can potentially impact your allowance. For example: UserA has been using Read Unread and Mark As Read read strategy for past 5+ months and currently has over 2000 emails residing in the inbox. However, the user has now decided to switch the read strategy over to Read All and Delete and the consequence of this turned out that all the mails residing in the inbox folder were processed by JEMHC which resulted to exceeding the allowance.  Potential impact - POP Mail Server configuration may override the instructions given by JEMHC. For example: read strategy (in JEMHC) has been set to Read Unread and Mark As Read and the Mail Server (POP) has been configured to Delete Gmail's copy once it has been processed. The end result of this would be the processed mail will be deleted from the inbox as per configuration.

Once the server details have been entered, click the Test configuration button to validate the connection. If the connection is valid, you will receive feedback similar to the below:

...