> For the complete documentation index, see [llms.txt](https://docs.livestreamiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.livestreamiq.com/readme/4.-administration/4.4.-email-configuration.md).

# 4.4. Email Configuration

The following section outlines how to configure email settings for notifications and alerts in the LivestreamIQ platform.

The following sections for email settings are:

#### 1. Email Information Section

![](https://1499573743-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6jSyTKzD9UG0uYLYFS7I%2Fuploads%2Fgit-blob-208f1d11c607239163bcb56430e7ec3d425036a4%2Funknown%20\(83\).png?alt=media)

Step - 1: From Email

1. **Purpose:** Specifies the sender email address that recipients will see.\
   Example: `alerts@company.com`
   1. Requirements:
      1. Must be a valid email address.
      2. Recommended to use an authorized domain email.

Step - 2: From Display Name

1. **Purpose:** Defines the sender name displayed in recipient inboxes.\
   Example: `Kafka Alert System`
2. **Recipient view:** `Kafka Alert System <alerts@company.com>`

Step - 3: Reply To Email

1. **Purpose:** Specifies the email address where replies should be sent.\
   Example: `support@company.com`

Step-4: Host to connect and authenticate

1. **Purpose:** SMTP server hostname or IP address.\
   Examples:
   1. **Gmail:** `smtp.gmail.com`
   2. **Microsoft 365:** `smtp.office365.com`
   3. **Outlook:** `smtp-mail.outlook.com`
   4. **Custom SMTP:** `mail.company.com`

Step-5. Port

1. **Purpose:** SMTP communication port.
2. **Common values:**<br>

   | Security Type  | Port |
   | -------------- | ---- |
   | SSL            | 465  |
   | STARTTLS       | 587  |
   | Unsecured SMTP | 25   |

Step-6: Security Options

1. Choose one security method.

   1. **Enable SSL:** Uses SSL encrypted connection.\
      Typical Port: `465`
   2. **Enable StartTLS**: Uses TLS encryption after connection establishment.\
      Typical Port: `587`<br>

   Recommendation: Use STARTTLS whenever supported.

Step-7: Enable Authentication

1. Toggle ON if SMTP server requires login credentials.
2. Most email providers require authentication.\
   When enabled, additional fields may appear:<br>

   | Field    | Description           |
   | -------- | --------------------- |
   | Username | SMTP account username |
   | Password | SMTP account password |

![](https://1499573743-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6jSyTKzD9UG0uYLYFS7I%2Fuploads%2Fgit-blob-2f20751bcbcb0b112d01472005d70a42d5938fb3%2Funknown%20\(84\).png?alt=media)

#### 2. Testing SMTP Configuration

1. Before saving the configuration:

Step 1: Click on the test Connection

Step 2: Following are the system validation:

1. System validates:
   1. Host connectivity
   2. Port accessibility
   3. Security settings
   4. Authentication credentials
2. Successful Result:\
   Example:\
   *Connection Test Successful*
3. Failed Result:\
   Example:

*Authentication Failed*\
*or*

*Unable to connect to SMTP Host*

4. Correct the settings and retest.

#### 4. Saving SMTP Configuration

After successful validation:

Step 1: Click on Create Config Email

Step 2: The system saves the SMTP configuration.

Step 3: The user will be redirected to the SMTP Configuration List page.

The new configuration will now appear in the list.

#### 5. Example Configurations

1. Gmail SMTP Configuration:<br>

   <table data-search="false"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>From Email</td><td>alerts@gmail.com</td></tr><tr><td>Display Name</td><td>Kafka Alerts</td></tr><tr><td>Reply To Email</td><td>alerts@gmail.com</td></tr><tr><td>Host</td><td>smtp.gmail.com</td></tr><tr><td>Port</td><td>587</td></tr><tr><td>Security</td><td>StartTLS</td></tr><tr><td>Authentication</td><td>Enabled</td></tr></tbody></table>

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong>: Gmail requires an App Password when 2-Factor Authentication is enabled.</p></div>
2. Microsoft 365 SMTP Configuration:<br>

   <table data-search="false"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>From Email</td><td>alerts@gmail.com</td></tr><tr><td>Display Name</td><td>Kafka Alerts</td></tr><tr><td>Reply To Email</td><td>alerts@gmail.com</td></tr><tr><td>Host</td><td>smtp.gmail.com</td></tr><tr><td>Port</td><td>587</td></tr><tr><td>Security</td><td>StartTLS</td></tr><tr><td>Authentication</td><td>Enabled</td></tr></tbody></table>

#### 7. Managing Existing SMTP Configurations

1. Navigate : **Administration → Email Configuration**
2. Available Actions:
   1. Edit Configuration:
      1. Locate the SMTP entry.
      2. Click Edit under Actions.
      3. Update required fields.
      4. Test the connection.
      5. Save changes.
   2. Delete Configuration:
      1. Locate the SMTP entry.
      2. Click Delete.
      3. Confirm deletion.

{% hint style="warning" %}
**Warning:** Deleting an SMTP configuration may impact email notifications.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.livestreamiq.com/readme/4.-administration/4.4.-email-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.