Updating an MTA domain configuration using the CLI

If a domain is configured with an incorrect next-hop address, incoming email to be forwarded to the incorrect address is deferred. To fix the problem, update the domain specification by replacing the incorrect next-hop address.

Caution
Do not delete an existing MTA domain in order to fix an incorrect next-hop IP address. Doing so deletes the email that was deferred for the domain.

This procedure describes how to use the Email Security - Server appliance CLI to update an MTA domain and next-hop IP addresses.

Prerequisites

An established connection between the Email Security - Server appliance and the Internet.
You are logged in to the Email Security - Server appliance CLI as an Admin or Operator.

To update a domain and next-hop IP addresses:

Go to CLI configuration mode.

hostname > enable
hostname # configure terminal

Overwrite the incorrect next-hop IP address with the correct value. In the following examples, the MTA domain is configured with the incorrect MTA IP address 10.11.121.14. The correct IP address is 10.11.121.13.
This example overwrites a single-hop MTA domain specification in order to fix the incorrect next-hop address:
```
hostname (config) # email-analysis xyzDomain.com next-hop 10.11.121.13
add next hop 10.11.121.13 to domain xyzDomain
Use default none for tls policy xyzDomain
```
This example overwrites a multiple-hop MTA domain specification in order to fix a single incorrect next-hop address:
```
hostname (config) # email-analysis domain pqrDomain next-hop 10.11.121.11 weight 60 next-hop 10.11.121.12 weight 20 next-hop 10.11.121.14 weight 20
Multiple next hops(3) configured for domain pqrDomain
Use default none for tls policy pqrDomain
```

Verify your changes.

hostname (config) # show email-analysis

Save your changes.
```
hostname (config) # write memory
```