E-mail notifications

E-mail transmite las notificaciones de alarma

Who receives e-mail

E-mail goes to recipients given as an e-mail address:

Sender	How to name an address
An alarm rule	{ "kind": "email", "email": "oncall@example.com" } in the rule’s notify.recipients. See Alarm notifications in depth.
A flow’s Notify block	A recipient row of kind address, one or more addresses separated by commas. cc and bcc add more; each gets their own message.

Recipients named as members, roles or teams are reached in the bell, by push and in their chat apps, not by e-mail. Name the address explicitly when you want mail. An address-only recipient has no preferences: they cannot switch the mail off in Hermetry, and quiet hours do not apply.

Account and security mail (sign-in codes, password resets, invitations) is addressed by the platform itself, to your account’s e-mail address.

The sender

By default, mail goes out from the platform’s own sender. An administrator can set your organisation’s own mail server and sender identity in Settings > Email (“Outbound email / SMTP configuration for this organization”):

Section	Fields
SMTP Configuration	SMTP Host, Port, Username, Password, Encryption
Sender Identity	From Name, From Email
Email Providers	Other mail delivery services, installed and configured as plugins from the marketplace.

If your configured server cannot be used, Hermetry falls back to the first mail provider that has credentials for your organisation. A flow cannot choose another sender (from).

Changing these settings needs Change email settings (Admin by default).

What the mail contains

Notification	Subject	Body
Alarm opened	“Severity alarm: title“	“Alarm “type” opened on device.”
Alarm escalated	“Escalated to Severity: title“	“Alarm “type” on device is now severity.”
Reminder	“Still open: title“	“Alarm “type” on device is open and not acknowledged.”
Alarm resolved	“Resolved: title“	“Alarm “type” on device resolved after n min.”
Storm digest	“n new alarms”	“n new alarms: 12 CRITICAL, 25 MAJOR.”
A flow’s Notify	The block’s subject, else its title	Its text, or HTML with format: html

Attachments from flows

A flow’s Notify block can attach files to the mail (other channels ignore them):

• at most 10 files and 1 MiB of file data per block; the mail queue accepts at most 10 files and 7 MiB per mail,
• the content comes from the message or the flow’s context, never fetched from a URL,
• an image can be shown inline with an inline_id and <img src="cid:…"> in an HTML body.

A bad file stops the whole call (invalid_attachment) rather than sending a different mail. See Alarm, command and notify blocks.

HTML mail

With format: html, the block’s text is sent as HTML after a strict clean-up: basic formatting, lists, tables, http/https/mailto links and cid: or https images are kept; styles, scripts, forms and frames are removed. Every other channel gets a plain-text form of the same HTML.

Quotas

Each mail counts toward your plan’s monthly e-mail quota (usage counter emailSends). When the quota is spent or your plan has no e-mail, a flow’s Notify block leaves e-mail out, says so in its result, and still uses the other channels. See Usage and quotas.

Addresses that are not mailed

Hermetry does not send to an address that is suppressed for your organisation, for example after a hard bounce or an unsubscribe, where your organisation keeps such a list. This applies to critical alarms too: a blocked mailbox stays blocked. The delivery log records each attempt and failure. See The notification log.

Troubleshooting

Symptom	Check
Alarm mail never arrives	Is the address named as an email recipient? Members and roles get no mail.
Mail arrives late	Mail is queued; a busy provider or a retry delays it.
Mail is in spam	Set From Email to an address of your own domain and configure your domain’s sender records with your mail provider.
A flow’s mail is missing	Check the block’s result: quota lists channels without quota; invalid counts bad addresses.

More: Troubleshooting notifications.