18.11: Application Setting Fields for ESP Version

Application Setting Fields for ESP Version

The ESP version of the MUMARA has slightly different fields for the application setting than the product version of MUMARA. The ESP version provides you the relevant fields to manage global SMTP settings and ability to take some security measures. The fields other than the discussed in the table followed by the figure below will remain the same as discussed earlier for the product version of MUMARA. The general application setting fields can be reached by clicking the link “Application Settings” of the product version.

Figure#18.10.1 ESP Application Setting Fields

Following Table Consists of

  • Text Fields  

Table#18.10.1: ESP Application Settings


The path to the SMTP server, the field requires verified information and is essential for the ESP to function properly. The path will further be used for the ESP clients to setup records like SPF and will be used as the SMTP host when the clients use their account as remote SMTP.  


Although IP address of your SMTP server can be used as the SMTP host to establish the connection, it is recommended for the ESP to use the domain instead of IP. It is more convenient and desirable for the clients of an ESP, to create records like SPF for the ESP domain and not for one of the IP addresses.  


When the client account setup wizard progresses, the SPF record takes the value setup here in the SMTP Host field. So if it is an IP address, the wizard automatically creates SPF record using the IP address.  And also the SMTP credentials provided to the client upon approval of his/her sender information will have an IP address as SMTP Host, which isn’t desirable. Therefore, the recommended practice is to provide a domain name for future convenience. 


Port25 is largely known as default SMTP port, but some ISPs has this default behavior to block port25. Therefore, MUMARA has made this field mandatory to fill with an appropriate port. It can be a port 25 or an alternative opening ports like 2525, 2526 (SSL) and 587.

The port that you will define here will also be provided to the clients of the ESP to use as an opening port while using their account as remote SMTP.

Server IP Address

Provide the ESP server IP to remotely access the server securely. The protocol secure socket shell ensures secure access to the remote server. For the ESP setup, you are requested to provide the IP on two places under “Application Settings” link. First for the field “Current Server IP” under “Application Setting Details”, and second in the field “Server IP” under “ESP Setup” on the right.


Don’t get confused, It would be the same IP which you have provided in the field for the “Current Server IP” under application setting details if PowerMTA is hosted on the current installation server of MUMARA (Local Server). You can also fill this field with “Localhost” if both the applications are on the same server. Recommended is to provide “Localhost” if PowerMTA is on the local server.  


But if PowerMTA server is different than the current installation server of MUMARA, provide here the IP address of the PowerMTA server that would be different from the “Current Server IP”.

Server Username

Provide the username of server for the SSH access, this supposed to be the installation server of PowerMTA. And as mentioned before, if PowerMTA is hosted on the local server, this would be the username of the current installation server.  Otherwise, the username of the server on which the PowerMTA is hosted.

Server Password

Provide the password associated with the username in the above field for the SSH access.

IP list for Admin Access

Provide one or multiple comma-separated lists of the IPs to allow them the admin access to PowerMTA monitoring. Only the IPs in this field will be able to access the PowerMTA monitoring at, and the access will be denied to all the requests coming from the IPs other than the ones in the field.