...
10:00 am theuser@mail.com processed (1 in the last hour)
10:10 am theuser@mail.com processed (2 in the last hour)
10:10 am somebodyelse@hotmail.com processed (1 in the last hour)
10:45 am theuser@mail.com processed (3 in the last hour)
10:50 am theuser@mail.combulk action taken (4 in the last hour)
11:20 am theuser@mail.com processed (3 in the last hour, first 2 don't count as they happened over 1 hour ago)
11:25 am theuser@mail.combulk action taken (4 in the last hour)
11:25 am theuser@mail.combulk action taken (4 in the last hour)
12:30 am theuser@mail.com processed (1 in the last hour)
How is the plan's data affected after processing an inbound email?
There are 2 streaming actions from/to JEMHC when processing an email. The first action is downloading the email from your email server. The second action is uploading every email attachment to your Jira or Storage instance.
As an example, if there is an inbound email to be processed with 2 attachments:
- 1 MB attachment to be uploaded to Jira
- 500 KB attachment to be blacklisted
The data cost of processing this email will be:
- ~1.5+ MB of email download (including the body of the email and attachment encoding cost)
- 1 MB of attachment upload to JIRA.
- ~2.5+ MB of data usage total.
This 2.5+ MB will be counted toward your monthly plan or removed from your data pack if you have used all your monthly plan.
How is the plan's data affected after sending an outbound email?
There are 2 streaming actions from/to JEMHC when sending an email. The first action is downloading the related attachments from JIRA. The second action is sending the emails with the attachments to each recipient.
As example, an user updates a Jira issue adding a 1MB attachment. There are 3 email recipients
- The assignee
- Two watchers
The data cost of sending this email will be:
- 1 MB of attachment download from Jira
- ~1+ MB of sending the email to the assignee (including the body of the email and attachment encoding cost)
- ~1+ MB of sending the email to the two watchers (including the body of the email and attachment encoding cost)
- ~3+ MB of data usage total.
This 3+ MB will be counted toward your monthly plan or removed from your data pack if you have used all your monthly plan.
JEMHC tries to send an email to multiples recipients when possible saving data usage and processing time. This cannot be achieved if:
- The configuration uses TO addresses instead of BCC. JEMHC avoids sending email addresses to users.
- The email body or attachments are different between the recipients.
In the example JEMHC was able to save data by sending the same email to both watchers. But it had to send another email to the Assignee as the email body is different (by default there is a 'Your Role Assignee' label in the body of the email).
What is the standard for Email Content structure, address structure, distribution list structure
...