Gmail outbound mail requires reauthentication through Captcha
The rules depend on if the message source is online/offline (connection, authentication problems, etc), the configured interval and when was the latest message processed.
Given the user interval in minutes (default is 1 minute) current strategy is:
You can tag JEMHC's email subjects with a Subject Prefix (like [JEMHCloud]) to you Message Outbound configuration (Messages -> Message Outbounds -> Pen/Edit Icon).
If you want to restrict a particular email address, you can do it going to Blacklisting -> Blacklist by Email Subject.
If you want to restrict users about how many emails they can send to JEMHCloud, you can set an hourly limit going to Profiles -> Your Profile -> Cog ->Edit and set up 'Sender is Bulk' message threshold. If the configuration is 3 (really low),
when JEMHCloud receives processable messages (valid addresses, no blacklisted, match catch, no procedence:bulk) what's happening is the following:
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)
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:
The data cost of processing this email will be:
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.
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 data cost of sending this email will be:
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:
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).
6.2.6. MULTIPLE MAILBOXES
An individual may have several mailboxes and wish to receive mail at whatever mailbox is convenient for the sender to access. This standard does not provide a means of specifying "any member of" a list of mailboxes. A set of individuals may wish to receive mail as a single unit (i.e., a distribution list). The <group> construct permits specification of such a list. Recipient mailboxes are speci- fied within the bracketed part (":" - ";"). A copy of the transmitted message is to be sent to each mailbox listed. This standard does not permit recursive specification of groups within groups. While a list must be named, it is not required that the con- tents of the list be included. In this case, the <address> serves only as an indication of group distribution and would appear in the form: name:; Some mail services may provide a group-list distribution facility, accepting a single mailbox reference, expanding it to the full distribution list, and relaying the mail to the list's members. This standard provides no additional syntax for indicating such a service. Using the <group> address alternative, while listing one mailbox in it, can mean either that the mailbox reference will be expanded to a list or that there is a group with one member.