> For the complete documentation index, see [llms.txt](https://docs.emaildelivery.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emaildelivery.com/docs/velocity-mta-basics/adding-a-server-in-the-backend-ui.md).

# Adding a server in the backend UI

{% hint style="info" %}
Velocity MTA servers list sending IP addresses that can be used for sending email when they've been added to an [MTA delivery policy](/docs/velocity-mta-basics/creating-an-mta-delivery-policy.md) and the policy has been added to a [postal route](/docs/introduction/postal-routes.md)
{% endhint %}

Go to MTA -> Velocity MTA Servers in the backend site navigation

<div align="left"><figure><img src="/files/RBni2CCH0frA9UhmNKeh" alt="" width="244"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Header domain**

Add the domain to use in the email headers for mail sent over each IP address&#x20;
{% endhint %}

{% hint style="info" %}
**Link domain**

Add the link domain that will be used in the email template body for mail sent over each IP address
{% endhint %}

{% hint style="warning" %}
The link domain must have a valid A record pointing to a Velocity MTA server IP address

**not** your platform installation address
{% endhint %}

<figure><img src="/files/pikyBYTGoi6JmWhtpt3Y" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**MTA Management IP URL**

The service URL must be the IP address of the management ip configured in velocity-install/conf/mta.conf
{% endhint %}

{% hint style="info" %}
**MTA Password**

The MTA Password must match the password in velocity-mta/conf/mta.conf on the Velocity MTA server exactly
{% endhint %}

{% hint style="info" %}
**MTA Management IP URL Syntax**

The URL syntax must start with http\://, then the management IP address, then :81 for the port

Example valid URL Syntax: [http://172.16.50.1:81\&#x20](https://docs.emaildelivery.com/docs/velocity-mta-basics/http:/172.16.50.1:81\&#x20);
{% endhint %}

<figure><img src="/files/BOaWh0wB5MTn1akZ5j9A" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
**Verify Velocity MTA received your server configuration**

On your server where the Velocity MTA container is running, begin monitoring the log file
{% endhint %}

```
tail -f velocity-install/logs/velocity.log
```

{% hint style="info" %}
Click save to push your changes
{% endhint %}

<figure><img src="/files/aK0eOt8wbu7mImeHwHB4" alt=""><figcaption></figcaption></figure>

If the service URL is set properly and the access key matches what's in the velocity-install/logs/velocity.log file, velvet.log should show something like the following

```
2023/06/08 23:46:45.879865 main.go:1039: :API:::172.16.50.1:38214 POST /settings
2023/06/08 23:46:45.881480 main.go:1136: :API:::Finished writing settings
```