Integrate your PowerMTA server with Mumara and let Mumara handle everything for you.
Menu Navigation: Setup - Sending Nodes - PowerMTA
Let's start setting up a PowerMTA Server...
Select your installed version of PowerMTA and insert your PowerMTA web monitor address in the correct format (e.g. 192.168.0.11:8080). Select the correct operator i.e. HTTP:// or HTTPS://. If you don't have a valid SSL installed on the PowerMTA web monitor.
Verify: Upon verifying the connectivity, if you get a failed status, it means the Mumara server has no access to your PowerMTA web monitor. To make it work, verify if you have added the Mumara server's IP to your PowerMTA config.
http-access 192.168.2.106 admin
If it still fails the connection, don't worry and you can still continue. Mumara will still overwrite everything at the end.
So now, let's connect with the server where you have PowerMTA installed.
Form Fields
| Field | Description |
|---|---|
| Server Name | Friendly name of the server for your identification purpose |
| Server IP | The main IP address of the Server |
| SSH Port | The port number to connect with SSH |
| Username | The username of the server (i.e. root) |
| Password | The password of the user |
| Operating System | Select the operating system installed on this server |
Verify: Verifying the connection to your server is mandatory here. If the server connection fails, Mumara will not be able to put up the configuration file and create the necessary folders.
Configure the SMTP settings that your Nodes will be connected with.
| Field | Description |
|---|---|
| SMTP Host | The hostname of the SMTP(s) that are being added as Sending Nodes. |
| SMTP Port | Port number of the SMTP connection that you want to be. |
| Mail Encryption | Set it to None if you don't want PowerMTA to encrypt your outgoing emails. |
Setup PowerMTA general and required settings by filling up the fields accordingly. We have pre-filled the default optimized values, just modify it if you really know what you are doing.
| Field | Description |
|---|---|
| Physical Path | The installed location of the PowerMTA Default: /etc/pmta |
| Management Port | The PowerMTA management port for the web monitor Default: 8080 |
| Admin IPs | IP addresses that should be given admin access to the PowerMTA web monitor. Default: Mumara server's main IP |
| Log File | The log file and the location to be stored at. Default: /var/log/pmta/pmta.log |
| Log Rotation | Specifies the number of files to keep when rotating the logging files. Default: 1 |
| Accounting Files | The name of the accounting files and the physical location to be stored at. Default: /etc/pmta/files/acct/acct.csv |
| Accounting Files Rotation | Delete accounting files after a specific duration Default: 7d |
| Diag Files | The name of the accounting files and the physical location to be stored at. Default: /etc/pmta/files/diag/diag.csv |
| Diag Files Rotation | Delete diag files after a specific duration Default: 7d |
| Spool Path | Define the location of the spool files where PowerMTA will queue the messages for delivery Default: /var/spool/pmta |
| Domain-Keys Path | The physical location of the folder where the private domain-keys will be stored Default: /etc/pmta/dkim |
| DKIM Selector | The default selector/prefix of the domain keys (e.g selector._domainkey.domain.com) Default: key |
| Tracking Domain Prefix | The default subdomain/prefix of the sending domain that will be used for tracking purposes. Default: click |
| VMTA Prefix | The prefix of the VMTA being created that will be incremented sequentially. Default: vmta |
| DKIM Fallback Domain | The default DKIM domain will be replaced as a signatory domain upon DKIM failure of the sending domain. Default: yourmumaradomain.com |
| Domain Key Size in Bits | The size of the domain key in bits that Mumara will generate for your sending domains. Default: 1024 |
Define the IP addresses and the sending domains that will be used for the email sending purposes. Mumara will generate the best combination of IP addresses over the domains on the next page that you'll have the ability to rearrange according to your requirement (if any).
| Field | Description |
|---|---|
| IP Addresses | The IP addresses added in your server that you want to get involved in email sending purposes. |
| Insert a Subnet | If you have a full subnet, add it in an easy way. |
| Sending Domains | The domains that will be responsible to relay emails. |
Drag the IP address to any domain panel to be used under the respective group. We have however divided the IP addresses equally for the best configuration. You have an option to create a single SMTP for all IP addresses within the group or to create an individual SMTP for every IP address.
| Field | Description |
|---|---|
| Domain name | The sending domain that will appear in mail headers |
| IP addresses | These are the IP addresses that Mumara will configure under the mentioned sending domain. By default, Mumara does the sorting itself by distributing an equal number of IP addresses among all sending domains, but you always have an option to resort according to your requirement by dragging to any palette. One SMTP account per IP: It will bind single IP to each SMTP account it will create One SMTP account for all IP(s): It will create a single SMTP account and bind all IPs to it and PowerMTA will handle the rotation |
| Group Name | The group name under which these SMTPs will be sorted |
| From Name | The sender's name that the email will appear to be sent from (if the sender-info is set to be fetched from sending nodes) |
| From Email | The sender's email that will appear in email headers (if the sender-info is set to be fetched from sending nodes) |
| Reply-to Email | The email address responsible to receive replies if the emails were sent from this Senindg Node |
| Bounce Email | The email address where the delivery status notifications of the failed messages will be sent by the MTA |
| Tracking Domain | The sub-domain that will mask/brand the hyperlinks and image source URLs in the email content body. |
Step 7: Configure Bounce Mailboxes
Configure the methodology of processing the failed deliveries. Mumara can two supported methods of processing the bounce reports for the PowerMTA addon
| Field | Description |
|---|---|
| Host | Hostname of the mail server where this email address is hosted |
| Port | Port number of the mail server to make POP/IMAP connection |
| Username | Username of the mailbox |
| Password | Password of the mailbox |
| Encryption | Choose the encryption method if your mailserver needs the connection to be encrypted |
| Method | Select from POP/IMAP (as advised by the mailbox provider) |
| Verify Connection | It verifies the connection with your mail server before processing ahead |
Turn the switch to disabled and Mumara will ask you to configure and connect with the bounce mailboxes responsible to receive delivery reports for the failed messages. If this process is selected, Mumara will perform the following tasks
If the switch is set to enabled, Mumara will not process the POP/IMAP method. Mumara will now look for the PowerMTA accounting files and do the following tasks
Note: In this case, Mumara processes delivery status for every record (not just failed messages)
Mumara generates Forward DNS, Reverse DNS, CNAME, and Domain Keys to get your sending domains authenticated. Expand the toggle(s) to get the values of the DNS entries for the sending domains. Moreover, you can click on the Download button and update them later.
| Field | Description |
|---|---|
| Host | This field contains the host key that is a prefix of your domain name. Make sure just to copy the host value (neglecting the main domain) to your domain's DNS panel as that is not necessary |
| Type | This is the type of DNS field e.g. A record, TXT, CNAME, etc |
| Value | While creating the host entry, paste the value of it |
It shows the configuration file that has been generated as per your inputs. If you want to tweak anything in the configuration file, you can do it in this step but make sure that you really know what you are doing.
This is the final step when Mumara starts configuring your PowerMTA installation.
Processes:
Once the PowerMTA has been successfully integrated, you should see the page as appears above.