How to retrieve the verbose MTA logs

This article explains the steps to help you enable verbose MTA logs for your on-premises instance if you are facing deliverability issues.

Description description

Environment

Issues/Symptoms

For on-premises instances facing deliverability issues, you may be asked for verbose MTA (Mail Transfer Agent) logs for examination to find the root cause of the problem. Here are some instructions to enable verbose logging.

Resolution resolution

To enable verbose MTA logs, follow the steps below:

Step 1:
Open the config-<instance-name>.xml file, where < instance-name> is the name of your instance.

Step 2:
Look for the following line in the file:

<mta autoStart="false" statServerAddress=""/>

Step 3:
Replace the above line with the following line:

<mta autoStart="false" statServerAddress="" args="-verbose -tracefilter:*"/>

Step 4:
Save the changes you made to the file.

Step 5:
Run the following command to check the configuration for any errors:

nlserver monitor -missing

Step 6:
After verifying that there are no errors, reload the configuration using the following command:

> nlserver config -reload

Step 7:
Stop all the mtachilds by running the following command:

nlserver stop mta*@instance_name

Note: The * in the command ensures that all the mtachilds are stopped.

Step 8:
Start the MTA process using the following command:

nlserver start mta@instance_name

Note: Replace <instance-name> with the name of your instance.