# Mail Server Settings

{% hint style="info" %}
**Important Note:** This article is for the **Org Administrator** in particular. The actions discussed in the article are not available to general users.
{% endhint %}

### Overview <a href="#overview" id="overview"></a>

You can use the mail server settings in this article to manually set up your email to send and receive an email with an iCloud email account. ARM requires mail server settings to send the ARM notification emails for events like build failures, build successes, deployment failures, merge reports, etc.&#x20;

Begin the process by hovering your mouse over the **`Admin`** module and selecting the option: **`Notifications`**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fb7vqzVp3tx4ONhescHHp%2Fimage.png?alt=media&#x26;token=a560b2f1-301e-4627-b48d-479ec0682be0" alt="" width="235"><figcaption></figcaption></figure>

You’ll then be presented with a screen divided into **`Mail Settings`**, **`Send a test email`**, **`Restricted Emails`**, and **`Teams/Slack Settings`** sections.&#x20;

#### Mail Settings <a href="#mail-settings" id="mail-settings"></a>

To set up a mail client, it’s necessary to configure the server to take care of your email delivery. And here’s the standard procedure for mail configuration and adding the correct parameters in the **`Mail Settings`** section:

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fmeiovc2iCsZUXdheQJPn%2Fimage.png?alt=media&#x26;token=1e9fcaf1-507d-4971-92cc-b6b2f4f7b551" alt="" width="536"><figcaption></figcaption></figure>

Fill in the required details as listed below (mandatory fields are marked with an asterisk (\*) mark.&#x20;

1. **`Host Name:`** Your incoming mail server name. *Ex- smtp.office365.com*
2. **`Port:`** The port number your incoming mail server uses. *Ex- Port 25*
3. **`User Name:`** The email address you want to set up. *Ex- <yourusername@autorabit.com>*
4. **`Password:`** The password associated with your email account.
5. **`Protocol:`** The protocol to manage the transmission and outgoing mail over the internet. If your email is encrypted using SSL, select the **`Use SSL/TLS if available`** checkbox.
6. **`Email From:`** Enter the email addresses you want to receive notifications while configuring the mail server.&#x20;
7. Select the **`Email Notifications`** checkbox to receive notification alerts.
8. **`Custom Email Template:`** ARM has its default email template styles, but you can also create your own. Enable the **`Custom Email Template`** field and add your logo at the top or bottom of the page. You can add footer text too. Once you're happy with your template, save it.
9. You can use the **`Reset`** button to clear all the data in the **`Mail Settings`** section and again fill in the fields.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FhoAnSIERVWJRnfaWMHnq%2Fimage.png?alt=media&#x26;token=f4ed52ae-3e25-493a-8fee-170d168b6797" alt="" width="563"><figcaption></figcaption></figure>

#### How to reset your mail preferences?&#x20;

You won't be able to switch back to the default ARM mail preferences once you have configured your email template. If you want to switch back to the default email style, please email us at [support@autorabit.com](mailto:%20support@autorabit.com), and we can do it for you.

#### Send a Test Mail <a href="#send-a-test-mail" id="send-a-test-mail"></a>

Before you use your customized email style, you can preview it once to make sure everything is showing correctly. Enter your email address in the **`Recipient`** field and click on the **`Test`** button to receive a test mail notification.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FQ3l5tgENOpimnsnMeQCM%2Fimage.png?alt=media&#x26;token=3b0df51f-de58-4f32-adff-d40f20df8819" alt=""><figcaption></figcaption></figure>

#### Restricted Emails <a href="#restricted-emails" id="restricted-emails"></a>

This section helps ensure that ARM-related emails are not sent to deactivated users who are no longer with the organization. Users in this list will not receive ANY emails, including deactivation, forgotten password, reset the password, jobs executed in the application, etc.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FhNdF1VzN0iAtLH5vYbSX%2Fimage.png?alt=media&#x26;token=1ed695a2-dc43-4120-ad84-f1a149937236" alt=""><figcaption></figcaption></figure>

The email address of a user who has been deactivated by an admin is immediately added to this list. If an inactive user is reactivated, the email address is deleted from this list. Enter the email address(es) for the user(s) to be added to the restricted list manually. The ’x' icon next to each user’s email address allows the admin to remove any user from this list. Click **`Save`** while adding or removing users manually.

To remove all users from the **`Restricted Emails`** list, click **`Delete All`**, and then click **`Yes`** to confirm.

Note: If you are not receiving any emails related to the application, you can contact your admin to check if you've been added to the restricted emails list. After the admin removes you from the list, you will receive any new emails from that point forward.

#### Teams/Slack Settings <a href="#teamsslack-settings" id="teamsslack-settings"></a>

When an event is triggered in ARM, email notifications are sent to the selected individuals. If you want to send notifications for particular events to an entire group within your organization through **`Teams`** or **`Slack`**, then integrate your Teams or Slack application with ARM using the respective **`Webhook Integration URL`**. For more information on configuring a webhook on **`Teams`**, click [here](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/webhooks/configure-a-webhook-in-teams). For **`Slack`**, click [here](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/webhooks/configure-a-webhook-in-slack).

1. Select either **`Teams`** or **`Slack`** as per your organization's requirements.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FgU0eK4koNABrA6pdwJ2N%2Fimage.png?alt=media&#x26;token=64878260-4a49-4e37-9a24-b824e042034a" alt=""><figcaption></figcaption></figure>

2. Enter a **`Channel Name`** and the **`Webhook Integration URL`**.&#x20;
3. Click on **`Test Connection`**. A **`Test connection Successful`** notification will be displayed.

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FTnNX0Ig903bPfuy6FLYs%2Fimage.png?alt=media&#x26;token=f81e67c3-16bc-432c-8cf2-c82d79e59a25" alt=""><figcaption></figcaption></figure>

   * If the test connection fails, an error message will be displayed. Check and re-enter the correct webhook URL.
4. After a successful test connection, click **`Save`**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FEfWPhLZ28fxaQqRIIjam%2Fimage.png?alt=media&#x26;token=e1a29269-0c34-4c9a-b780-8a914009a481" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Important Note:** The first channel you add is automatically configured to all the events by default. To remove the channel from any notification type, click on the![](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FjN77D0yosm7L5RtKpEhd%2Fimage.png?alt=media\&token=dc0a4544-c291-49dc-a562-5bbfc1e5d603)icon. Channels added after that will have to be configured to events manually.
{% endhint %}

5. Click on the **`+`** icon to add another channel. You can add up to **10** channels.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FwJ9ntQe82OFgZzZ60LMq%2Fimage.png?alt=media&#x26;token=204bb0cf-5daf-4837-93b0-704828ed9d20" alt=""><figcaption></figcaption></figure>

6. Click the **`x`** icon to delete a channel and click **`Yes`** on the confirmation message.

**Notification Configuration**

This section is a guide to configuring the channels to the notification types. You can select which group(s) on Teams or Slack should be notified when a particular event is triggered.&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FSVuoDqWeuuiZNsWOAicL%2Fimage.png?alt=media&#x26;token=6b32b309-3d37-4a26-9708-985750141494" alt="" width="563"><figcaption></figcaption></figure>

1. Select the checkbox for the **`Notification Type`** that you want to configure.
2. Click the **`Selected Channels`** field to display a list of configured channels.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F809PynFN0Acz5MPV5iG5%2Fimage.png?alt=media&#x26;token=bd4baa2c-f631-4fd4-875d-0d965bee8654" alt=""><figcaption></figcaption></figure>

3. Click the channel that you want to send the notification to when this event is triggered. You can select up to five channels for each notification type, meaning you can select as many channels as you have configured.
4. You can select multiple checkboxes for numerous notification types and select the channels to which you want to send notifications for each event.
5. Click **`Save`**. All the selected **`Notification types`** will be saved simultaneously.&#x20;
6. When an event is triggered in ARM, the configured channels will receive a notification.\
   The image below is an example of what these notifications look like on Teams.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FdoKNy9GAonw05I0Afnhx%2Fimage.png?alt=media&#x26;token=3a3efe29-6b0e-46cf-9e54-6206caeb0c54" alt="" width="554"><figcaption></figcaption></figure>
