19.3: Add Sender Information

Formerly it was client account setup wizard that performs all the SMTP, sender information and email authentication stuff alone, but now the account setup appears on the dashboard and deals with SMTP only, and during the latest upgrades, the sender information and email authentication section has been moved to the left navigation menu. Click "Add Sender Information" the link under "Dashboard" in the left navigation menu of the client.

Upon clicking "Add Sender Information" from the left navigation, you will be taken to the page where you will be able to view the list of currently available sender information and its status as Approved or Pending. To add new sender information, you will click "Sender  Information" at the top right side of the table, also shown the figure below. 

Figure#19.3.1: Currently Available Sender Information

Sender Information

During the course of the wizard, you will learn that the clients can send either by using the domain setup by the ESP, or even from their personal domain by implementing the corresponding DNS records. The latter type of sending using client's own domain is known as "White Labelled Sending". Other accounts can be categorized as Non-White Labelled accounts. 

a) Non White-Labelled Senders

The sending servers for the ESP Edition of Mumara are configured with basic sending domain, DKIM Fallback Identity and Domain, and other required configuration measures. So if the client account selects to send as non white label sender, the emails will be sent using the ESP basic sending domain, and switches to DKIM fallback identity if DKIM fails to pass.

So in case you don't tick the checkbox option in the wizard to subscribe to "White Label Sending", you will just need to fill in the following fields. 

1) Sender Email

The emails will be sent using the email address in this field.The recipient of the emails, relayed from that particular client account, will be able to view “Sender Email” in the from email field of their email client. 

2) Reply Email

Email address to which recipient will be sending replies, when the recipient decides to reply, this email address will automatically be inserted into "To" field. 

3) White Label Sending

If you are setting up your account as non-white label sender, proceed without ticking the checkbox/ 

4) SMTP Account

You will be offered two radio buttons to select one of the options between the following two.

4.1) Existing- Click to open a dropdown consisting of the currently available SMTPs, select one of the already existing SMTPs to be used with this sender information. 

4.2) New- Click to open the fields to provide "SMTP Username" and "SMTP Password" for the new SMTP. Upon getting approved from the support staff user, the new SMTP will become operational with this sender information. 

That's it, the non-white labelled senders just required to fill this part of the wizard, upon pressing "Next', they will be able to see the success message. Once this sender information account is approved, client will be able to send emails using SMTP and its corresponding sender information. 

Figure#19.3.2: Non-White Label Senders

Non White Labeled Accounts

b) Setup White Label Sending

Above we have discussed the first option of sending from the ESP domain; the second option is to white label client's account. In this process, client will be using his/her own sending domain, and implement required email authentications during the course of this wizard. The process consists of more than few well knitted steps, and starts from the basic sender information fields. 

1st Step-Basic Sending Details 

The first step of white label sending is similar to what we have setup for non-white label senders, except for the addition of one new field called "Bounce Email". As soon as you tick the checkbox for "White Label Sending", the field for "Bounce Email" appears on your screen. 

Figure#19.3.3:Sender Information for White Labelled Accounts

White Labeled Accounts

1) Bounce Email

It is going to be the bounce to email account and the bounced back emails will be sent to this email address. Provide the bounce to email address that belongs to the same domain in "Sender Email" and "Reply Email" fields.

If the domain of the bounce to email address is different from the sender email and reply email, DKIM would most probably will fail to get authenticated. In this case, application automatically switches the primary DKIM to the DKIM Fallback Domain, it will however lowers down the sender score.

Therefore, the suggested practice for the white label senders it to create bounce to email address on same domain using which they have created "Sender Email" and "Reply Email". Later in this wizard, this domain will be used to create the CNAME and other TXT records. It is how the application will let you validate the information, and authenticate the sending information appropriately.

Rest of the fields in the first step will remain the same as discussed above for non-white label senders. 

The  bar indicates the progress of the wizard, and at the first step of the wizard, it remains 25% filled and with the red color. Remaining 75% of the progress bar will complete during the course of next steps of the wizard.

2nd Step- Bounce Settings 

The second step of the wizard is about configuring your system for bounce processing, and the following fields appear on your screen.

Figure#19.3.4: Configuring Bounce

Setup Bounce Mailbox

1) Bounce Host

Fill in this field with the path to your mail server or you may say the server where Bounce to email address resides. This path is required to establish the connection between the application utility and server, and further helps in effective processing of bounced emails.

The host or path to your email server or bounce email server generally looks like, and bounce can also be the IP address of your bounce server.

Application will automatically generates and proposes the common structure of bounce host, by taking domain name from the bounce email address, you earlier have provided in the “Bounce Email” field while completing the first step of the wizard.

2) Bounce Processing 

You are offered with the two options to choose one of them, both post office protocol (POP3) and internet access messaging protocol (IMAP) are the protocols used to access emails on remote server.

Both IMAP and POP are different in working mechanism and scope, like the POP3 is somewhat secure as it allows downloading of the emails from the server or checking of the emails using one computer/ device. While the IMAP allows using multiple devices, computers for the same process, therefore select accordingly.

3) Bounce Port

Application automatically fills that field with default opening port, according to your selection of IMAP or POP.  Default port for IMAP is 143 and 110 for POP3 (Without SSL or Non-Encrypted).

But if it is a port other than the default ones, mention it here in this field, by removing the default port proposed by the application, and specifying yours.

4) Bounce Password

Password of the bounce to email address that you have provided in "Bounce Email Account" field, while completing the first step of the wizard.

3rd Step-Setup Masking Domain

Here comes the step to settle with the sending URL, it also refers to as Masking Domain. Let’s discuss both the terms.

Sending URL/Tracking URL-

The emails will be sent from that particular URL, and the recipient of the email will be able to view this URL as sender or mailed by domain. Later in the next step of this wizard, we'll be using this domain to mask the ESP's primary sending domain. So typically the URL will go along as tracking URL, in the emails that particular client will send.

The domain part of the tracking URL isn’t editable, and it has automatically been obtained from the domain mentioned with “Sender Email”, as sending email domain, the sending/tracking URL domain has to be the same for valid identity.

The empty box before the domain name is for client to provide the selector value to be used with domain name. Both selector and domain together constitutes the complete structure of the sending URL. The selector is also known as prefix, alias, host or simply selector. Selector can be anything like, send, link, etc. Press next after filling the selector area.

Figure#19.2.5: Setting Up Sending URL

Tracking URL

4th Step- Implementing DNS Records

Start setting up the DNS records as per the recommendation wizard has returned with. Mumara follows a fully automated process to generate the values with appropriate entries for the DNS zone to implement the record correctly. 

Figure#19.2.6: Implementing DNS Records 
DNS Records

1) DKIM Record

First entry in the process of implementing the DNS record is DKIM authentication (Domain Key Identified Mail). The entry under host field is automatically generated with the corresponding selector/ prefix, by taking it from the sending URL you have provided in the previous step.

Selector is the attribute for the DKIM signature, used with the domain name to manage and support multiple keys for the same domain. It adds a differential attribute with each public key you generate for the same domain; however the validation process considers selector as additional attribute in the signature. For most of the people, one selector is enough to pass their authentication and keep their work flow smooth, except for the organizations with administrative divisions and diverse staff roles.

They can use anything as selector, like individual user names, department names, locations of geographically dispersed offices of an organization, or even the joining dates of the employees. But as most of the clients don't need to use multiple selectors for the DKIM record of the same domain, therefore a selector might readily been selected by taking it from the host/selector/prefix field of the sending URL.

You can provide your own preference for the selector in the small text box with sending URL field during the 3rd step of the wizard. Whatever you will put into the box, application will take it as the selector, to create the entry for the related records.

Now as the application has returned with DKIM values and public key to be configured into the DNS, it is right time for you to learn putting the values in the DNS of the sending domain, side by side. All you need to do is copying the values and putting them appropriately in the relevant fields of the sending domain DNS.

Access the DNS of the sending domain, The DNS interface for different control panels appear slightly different than one another, but still you will be able to locate the elementary fields in all the control panels, including Cpanel, Plesk or CloudFlare etc.  You may reach the required page to edit DNS setting and to configure the record by clicking “Advance DNS Zone Editor” in Cpanel, and “DNS Settings” for both Plesk and CloudFlare. However, we’ll be using Cpanel during the course of the discussion.

DNS Entry of DKIM Values

Reach the DNS of the relevant domain (In Sender Email and Sending URL), “Advance DNS Zone Editor” in case of Cpanel. Once you are in at “Advance DNS Zone Editor” you’ll find 3 text fields along with the dropdown to select the type of the record you are adding. Here are the fields that you need to fill in order to add a new record. The table followed by the figure below discusses the information which you need to add in the respective fields to add a public key appropriately into the DNS of Cpanel.

Figure#19.2.7: DNS Entry of DKIM Record 

Table#19.2.3: Adding a TXT Record (DKIM)


The source field needs to be filled with the domain name, if you write down only the selector, the field automatically detects the domain to complete the entry. 

Mumara comes up with a complete DNS entry under “Host” during the step "DNS Records" of the wizard. Where you need to just copy the value from the relevant “Host” field in the wizard, and paste it into the “Name” field of the DNS.

It is recommended to copy the value created by the application according to your sending domain, instead of doing it manually.


Figure#19.2.8 demonstrates the copying of the host field 


It refers to the Time to Live for the DNS entry, and the field needs to be filled with positive integer, which indicates that how long the DNS entry should be cached by the client( In seconds).  The default TTL varies from DNS to DNS, however in Cpanel the default TTL is 14400 (In second)


Select TXT from the dropdown as the type of record you are about to add. A domain may have more than a few TXT records which includes DKIM or SPF etc. The TXT records are usually used to carry human readable information about the network or server etc.  Choose TXT and move to the next field.

TXT Data

The final field needs to be filled with the public key generated by the application. Copy the public key from the application and paste it into the related TXT data field. See the Figure#19.2.9: Copying the Key followed by Copying the Host Value .


Figure#19.2.8:Copying Host Field Value

Figure#19.2.9:Copying the Key
DKIM Value

Once you are completed, click “Add Record” (Domain DNS )to save and update DNS settings with new record. The client just needs to configure the public key into the DNS; if the ESP’s PowerMTA server configured appropriately with Mumara, it automatically generates the private key for this public key to complete the pair and pass the authentication. 

2) SPF Records

After completing the process of adding DKIM record into the DNS, move forward to the 2nd field underneath, to create another TXT record. The 2nd important email authentication in the wizard is known as SPF. Sender policy framework or simply SPF is a method devised to curb the forgery of email by authenticating the sender domain. Implementation of the SPF helps recognizing which server is authorized to send email on behalf of particular domain. The ultimate gain of implementing of the SPF record into the DNS is that it prevents spamming, and discourages forgery of the email.

For example, your domain uses an ESP to send emails. You need to create the SPF record using the DNS of your domain, it should verify that the mail server of the ESP domain ( is authorized to send on behalf of your domain ( The email client of the recipient will check the SPF to establish the authenticity of the server as legitimate sender. The following area discusses setting up an SPF record using Mumara ESP Edition

DNS Entry of SPF Values

Unlike DKIM and CNAME, SPF doesn’t need additional attribute in its value to setup the record; therefore, the value under “Host” in the wizard isn’t starting with additional value with the domain name. The process of adding a SPF record is almost the same as described above for the DKIM. Reach the DNS zone of your domain, and add a new record. See the above mentioned Figure#19.2.7 that shows the fields of the DNS to enter new record information in the CPANEL.

Table#19.2.4: Adding a TXT Record (SPF)


The name field should be filled with the domain name for which you are creating the SPF record. It would be the complete qualified URL of It would obviously be the same domain for which you have setup the DKIM.  However, you are recommended to copy the value from the wizard and just paste it here, as the wizard returns with an appropriate entry according to your domain. Figure#19.2.10, illustrates copying of the host field value from the wizard to put into the name field of the DNS. 


It refers to the Time to Live for the DNS entry, and the field needs to be filled with positive integer, which indicates that how long the DNS entry should be cached by the client( In seconds).  The default TTL varies from DNS to DNS, however in Cpanel the default TTL is 14400 (In second).


Select TXT from the dropdown as the type of record you are about to add. A domain may have more than a few TXT records which includes SPF and DKIM etc. The TXT records are usually used to carry human readable information about the network or server etc.  Choose TXT and move to the next field.

TXT Data

Now to authorize the ESP server to send on behalf of the domain you have just entered in the name field, copy the SPF record value from the wizard to put into the DNS entry. MUMARA generates the SPF record for ESP domain and all sending IPs, instead of generating a record for specific IP or IP range, this word `all in the value of the record ensures that even if the ESP changes the sending IPs, you will still continue to get your SPF passed, unless the ESP domain changes, which seldom happens. The wizard generates the value covering all the vulnerabilities, therefore it is recommended to copy the record the wizard and paste it here. The Figure below 19.2.11 shows copying of the SPF value from the wizard.


Figure#19.2.10: Copying Host Field Value 
SPF Host

Figure#19.2.11: Copying Record for Data Field 
SPF Data Value

3) CNAME Record

After completing both the TXT records, now it is time for the client to setup another type of record in the DNS called CNAME.  All these records including DKIM, SPF and CNAME are important for the clients to validate his/her identity as legitimate sender. Therefore setup accordingly, as the white label senders won’t be able to get their accounts approved from the ESP's support staff user, until they have implemented all these records appropriately.

DNS Entry of CNAME values

You are required to manage the things from the DNS, and the interface of the DNS may vary depending on your control panel (Cpanel, Plesk or CloudFlare etc). As we have been discussing the implementation of the records in our test case that is setup with the Cpanel, therefore here we are in “Advance DNS Zone Editor”. You can create CNAME using administrative tools provided by the domain host, depending on your accessibility and convenience. The fields to add CNAME record in the DNS are discussed in the table after the figure below.

Figure#19.2.12: Adding CNAME Record
TXT Cname DNS Record

Table#19.2.5: Adding a CNAME Record


The “Sending URL” and the selector text in the small text box before the sending URL during the Masking Domain step of the wizard, creates the value under “Host” field of the wizard for CNAME. The field of the Name, Host, or Alias in the DNS needs to be filled with the sending URL. The simple way of doing it is to copy the value from the wizard and paste it in the relevant field of the DNS. The following Figure#9.8.13 shows how you will copy the value from the wizard to fill into the relevant DNS field. 

The field in the DNS may auto detect the domain even by providing just the selector. However, it is still advised to copy the value from the wizard and paste it in the field, to avoid confusion and possible error.


It refers to the Time to Live for the DNS entry, and the field needs to be filled with positive integer, which indicates that how long the DNS entry should be cached by the client( In seconds).  The default TTL varies from DNS to DNS, however in Cpanel the default TTL is 14400 (In second).


Select CNAME from the dropdown as the type of record you are about to add. As mentioned earlier, the CNAME record is used to map a name with another name. Select CNAME and move to the last field to complete the record entry.  


The domain with the corresponding selector in the above field of "Name", will point to the domain you will enter in this field. The Sender Information Wizard recommends you the complete URL to copy and put it into the field of CNAME. It would be the ESP domain suggested during the configuration of "Sending Server". Your Sending/Tracking URL will actually point to this domain.

However, as everything has been precisely setup until now, to keep it smooth, just simply copy the record from the wizard and paste it in the relevant field of the DNS (CNAME in case of Cpnael).

 See Figure#19.2.14: Copying Domain/Value for the CNAME


Figure#9.8.13: Copying Host Field Value 
CNAME Host Value

Figure#9.8.14: Copying CNAME Record for the Data Field 
CNAME Data Field Value

Save the changes by clicking “Add Record” to update the DNS zone with this new CNAME entry. After entering all the values into the relevant records in the DNS, press next in the client account. setup wizard to move to the 3rd to verify the records. 

5th Step:Verifying the DNS Entries

After completing required DNS entries with the corresponding DKIM public key, CNAME for masking domain and SPF to authorize the sending server to send on behalf of your domain, click “Next” to start verifying process of the DNS entries. The process of verifying the DNS entries starts as soon as you click “Next”, Figure#19.2.15 shows how it looks when the application is in process of verifying the DNS entries.

Figure#19.2.15: Verifying DNS Entries Verifying DNS Entries

If the application verifies all the entries successfully, application will put the following screen on display.

Figure#19.2.16: DNS Entries are Successfully Verified
Successfully Verified DNS Entries

Similarly, when the application remains unable to verify the DNS entries or one of them, it returns with the following error screen.

Figure#19.2.17: Unable to Verify DNS Entries
Unverified DNS Entries

If the application verifies the accuracy of the DNS entries during the processing of the wizard, final step puts a success message on display. Otherwise, you will get an error message and wizard will not progress to the final step. Make sure that if the client account has not been verified for the DNS entries, the management and support staff of the ESP will not approve the client account, and unapproved accounts will not be able to send emails.

Approved Senders

After successfully providing all required information in the client account setup wizard, and having been verified for all the DNS entries including DKIM public key, CNAME record, and SPF record, client account goes to support staff user of the ESP for the approval. The support staff user checks verification status of the sender information and DNS records provided by the client. If the client has verified for the DNS entries, support staff user approves his/her account.

The approved clients will be able to view their SMTP details right on their dashboard. Once the client is approved by the support and management staff of the ESP, the client can start using the email credits in his/her account right away, and also will be able to use the SMTP remotely. In order to use it as remote SMTP, you would need SMTP host, opening port, SMTP username and password. The approved client will be provided with all the required information upon approval of his/her account. The following figure indicates the position of SMTP account information on the dashboard of an approved client.

Figure#19.2.18: Approved Client’s SMTP Details
Approved Sender Info