Blog from March, 2024

Within the latest release (v1.3.419), a bug has surfaced where emails leading to a Forward Outcome are not being removed from the Mailbox. Consequently, they are being repetitively processed, eventually causing the Mail Handler to be blocked.

If you encounter this bug, the only way to unblock your Mail Handler is to access the relevant Mailbox and deleting the problem email. Once this is deleted you will then be able to go to JEMHC > Messaging > Message Handlers and press “Release” to unblock the Mail Handler.

We are currently investigating this. We update this blog when a fix has been made.

Update 21st March: https://status.thepluginpeople.com/incidents/6l1d6m94h2cj incident has been created to track changes. We are currently fixing the changes causing partial outage, and all blocked handlers will be automatically unblocked.

We recently launched Data Residency support for EU and DE (Germany) Atlassian product regions.

If your JEMHC installation is in the EU and DE app data location, you may need to adjust any IP-based security rules that your email/communication services have to allow JEMHC to connect.

Here is the latest full list of IP addresses used by the app:

54.210.55.45
54.210.87.155
54.218.180.167
44.229.69.164

18.199.53.18
3.72.144.3
99.80.78.158
63.35.49.84

What has changed?

• The setting Catch Email Headers found in the top level of profiles has been renamed to Additional Recipient Headers to better reflect its true functionality

• By default, JEMH Cloud now also checks the Delivered-To email header so you no longer need to set it as an additional recipient header. JEMH Cloud will check the following headers automatically:

  • To

  • Cc

  • Bcc

  • Delivered-To

  • Newsgroups

Atlassian have a Data Residency feature which allows customers to control what location their Jira product data is hosted in.

We are happy to announce that JEMH Cloud now supports data residency for Jira Cloud products that are located in US, EU and Germany locations as per Atlassian documentation. For more information on JEMH Cloud and Data Residency, see here: Data Residency .

What does this mean?

• For existing app installations, your app data will remain in its current location (the US). We plan to support data migration in the near future.

• For new app installations, your app data location will be different depending on where your Atlassian product data is located:

What about migration of app data to another location?

We have plans to offer application data migration so that existing customers can move their JEMH Cloud data after changing the location of their Atlassian product data. This should be arriving in early Q2 this year. For updates on migration support, watch this blog.