Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We have been adding some configuration section-exports in JEMH, (e.g. image blacklisting) but as yet have not added the import aspect to JEMHC.

Things to consider

...

JEMHC Capacity Plans

Your JEMHC subscription drives an allocation (1st of every month) of a Capacity Plan based on the number of subscribed users, ; as your users increase, so does message volume and data capacity. If you consume the allocated plan, inbound mail and outbound notifications stop. No data is lost, it just remains queued.

Getting more message volume and data

Regardless of cause, if you consume your plan then JEMHC capacity plans have gone up frequently, they are sufficient to solve most users capacity needs. If your are in an edge case of low-users, will stop processing mail, more capacity can be purchased through Data Packs as needed, for through a 12 month term Plan Upgrade.

Typical cases are where you can be impacted are where you have relatively low-users and relatively high message volume/high data capacity, . JEMHC has options, through the purchase of Data Packs (:

Data Packs & Plan Upgrades

Data Packs provide an on-demand short term Message and Data increases) as well as volume increase. Plan Upgrades provide a 1y term Plan Upgrades to gain higher capacities normally attributed to a higher number of users on a monthly basis. Both Data Packs and Plan Upgrades are purchased out of band from Atlassian Marketplace as it has not yet matured to support such app-specific metrics (see Licensing for details).

Limiting message volume usage

Related to message volume, JEMHC delivers its notification by BCC to limit the numbers of mails JEMHC needs to send through your mail server. Switching this to TO will increase message volume.

Related to message data, JEMHC does support inline images in outbound notifications, and attachments, if you enable this, and make regular use, it can impact your data usage.

Mailservers

JEMHC cannot use the mailbox provided by Atlassian, you must use an external one, when doing so you may need to refer JEMHC public IP address to allow contact to your instance - this allows anyone on JEMHC to attempt this, for finer grained security, you would need to setup dedicated certificates that only your configuration has.

...