> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarme-regeln-und-eskalationen/eskalationen/notification-provider/mail.md).

# Mail

The notification provider *Email* In Eliona, it enables the configuration and management of email notifications to send alarms and other notifications via an email system.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/ZmgDy7HsUJkpMVElVsbZ/email.png" alt=""><figcaption></figcaption></figure></div>

## Configuration

Navigate to:\
**Engineering → Notification Providers → Email**

In the view **\[A]** the following options are available:

<table data-full-width="true"><thead><tr><th width="66.19998168945312">No.</th><th width="270.20001220703125">Field / Option</th><th>Description</th></tr></thead><tbody><tr><td>A1</td><td>Note</td><td>Internal note for this configuration.</td></tr><tr><td>A2</td><td>Host</td><td>SMTP server through which emails are sent.</td></tr><tr><td>A3</td><td>Sender Name</td><td>Name displayed as the sender in emails.</td></tr><tr><td>A4</td><td>Sender Email</td><td>Email address used as the sender.</td></tr><tr><td>A5</td><td>Authentication required</td><td>Enable/disable whether SMTP authentication is used.</td></tr><tr><td>A6</td><td>Users</td><td>Username / email address for SMTP authentication.</td></tr><tr><td>A7</td><td>Password</td><td>Password for SMTP authentication.</td></tr><tr><td>A8</td><td>Port</td><td>SMTP server port (e.g. 25, 465, or 587).</td></tr><tr><td>A9</td><td>Pool</td><td>Enables sending via an SMTP pool.</td></tr><tr><td>A10</td><td>Secure</td><td>Enables the use of a secure connection (STARTTLS/SSL).</td></tr><tr><td>A11</td><td>Strict SSL/TLS</td><td>Forces a strict SSL/TLS connection.</td></tr><tr><td>A12</td><td>Rate Limit</td><td>Maximum allowed number of emails per defined interval.</td></tr><tr><td>A13</td><td>Rate Delta</td><td>Time interval for the rate limit in seconds.</td></tr><tr><td>A14</td><td>Max Connections</td><td>Maximum number of concurrent SMTP connections.</td></tr><tr><td>A15</td><td>Save</td><td>Apply changes to the configuration.</td></tr></tbody></table>

{% hint style="info" %}
Make sure the SMTP server is set up correctly, otherwise no emails can be sent.
{% endhint %}

## **Email Templates**

Eliona allows you to customize individual email templates for various notifications. This applies not only **Alarm Emails**, but also ***Ticket Email Content*** and ***Password Reset Email Content***. By customizing these templates, you can tailor the design, style, and content of your emails to your needs.

Click on <img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/EXPvmDjCj4oXeFyuvddV/image.png" alt="" data-size="line"> on the right in the **template \[C]**, to edit a pre-made template.

{% content-ref url="/pages/8894b3c86580a6b6b9cdac807e96502026afb725" %}
[Twig templating in Eliona](/collection/english-v14/academy/twig-templating-in-eliona.md)
{% endcontent-ref %}

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/YErItK8uwcTEfcjds8Lc/email%20(1).png" alt=""><figcaption></figcaption></figure></div>

### **Override default**:

To customize the selected template, choose the option **Override default \[D]** This allows you to make individual changes to the template instead of using the default template.

### Change email subject

As soon as the option **"Override default"** is activated, you can customize the email subject **\[E]** Enter a custom subject here, which will be used for all future alarm emails.

◈ *Only alarm variables can be used in the email subject:* [→ Alarm template: Available variables.](/collection/english-v14/academy/twig-templating-in-eliona.md#alarm-template)\
▷ *The subject of ticket and password reset emails is fixed and cannot be changed.*

### **Edit format & style**:

{% hint style="info" %}
You can find which variables can be adjusted here: [↗ Templates](/collection/english-v14/academy/twig-templating-in-eliona.md)
{% endhint %}

Under **Alarm Email Content \[F]**, **Ticket Email Content** or **Password Reset Email Content** you can edit the HTML code of the respective email. This code determines the layout, colors, and structure of the email.

**Alarm Email Content**: Used for notifications sent via triggered alarms.

**Ticket Email Content**: Used for emails sent as part of the ticket system, e.g. to inform about newly created tickets or status changes.

**Password Reset Email Content**: This template is used for password reset emails when a user resets their password.

With HTML and CSS you can make changes to the design and formatting, such as the font, colors, or inserting images:

```html
<h2 style="color: #4CAF50;">New Alarm: [Alarm Type]</h2>
<p>An alarm was triggered at [Alarm Time].</p>
<p>Details:</p>
<ul>
  <li><strong>Alarm ID:</strong> [Alarm ID]</li>
  <li><strong>Priority:</strong> [Alarm Priority]</li>
</ul>
```

After you have edited the template, click **Save,** in the bottom left to ensure that all future emails use the updated content.

{% hint style="info" %}
Test the customized template after every change to ensure that it is displayed correctly and contains no syntax errors in the HTML code.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/english-v14/documentation/alarme-regeln-und-eskalationen/eskalationen/notification-provider/mail.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.