​

1) SPF ( Sender Policy Framework ) : SPF stands for "Sender Policy Framework".  An SPF record is in place to identify which mail servers are authorized to send mail for a given domain. It is used to prevent spammers from sending mail with fraudulent From addresses in that domain. Though many DNS editors allow for the creation of an SPF record, the SPF record must be entered as a TXT record in your domain's DNS settings create a TXT record. Enter:

Record Type : TXT

Host - @

Values - v=spf1 a mx include:mailerswift.app ~all

 

2) DKIM ( "DomainKeys Identified Mail" ) : DKIM stands for "DomainKeys Identified Mail". They allow receiving servers to confirm that mail coming from a domain is authorized by the domain's administrators. Create a TXT record. Enter:

Record type : TXT

Host/Name: api._domainkey

Value: k=rsa;t=s;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCbmGbQMzYeMvxwtNQoXN0waGYaciuKx8mtMh5czguT4EZlJXuCt6V+l56mmt3t68FEX5JJ0q4ijG71BGoFRkl87uJi7LrQt1ZZmZCvrEII0YO4mp8sDLXC8g1aUAoi8TJgxq2MJqCaMyj5kAm3Fdy2tzftPCV/lbdiJqmBnWKjtwIDAQAB

 

3) Tracking : Mailerswift "tracks" opens, clicks, unsubscribes, etc.  To do that we must rewrite links and use web pages.  Setting up a "tracking domain" brands these rewritten links and pages with your own domain. Create a CNAME record. Enter:

Name: tracking

Type : CNAME

Value: tracking.mailerswift.app

​

​

​

​

​

4) MX : For most users, you will not be adding or changing any MX records in your domain's DNS. The only reason why you would change or add an MX record for use with Mailerswift is if you are using Inbound Email Notifications which are webhooks that are part of our HTTP API. Otherwise, this will give you a green check mark if you have an existing MX record that is used for directing mail to your own mail server. If it does not give you a green check mark when you do not have any MX records for your domain. This is OK - it is not required and all it means is that you do not currently have a mail server setup for your domain.

​

Eg - Set up MX records for Google Workspace email

​

Record Type : MX

​

Host : @

​

TTL : 3600

​

Priority : 1

​

Values : ASPMX.L.GOOGLE.COM

​

​

 

 

 

5) DMARC : Domain-based Message Authentication, Reporting & Conformance is an email authentication protocol that is built on top of SPF and DKIM protocols.  SPF and DKIM are prerequisites of DMARC and must be in place before setting up a DMARC policy. A DMARC policy allows a sender to indicate that their emails are signed by SPF and DKIM and tells a receiver what to do if neither of those authentication methods passes – such as junk or bounce the email.

​

The following are example DMARC TXT entries to set up on your domain(s) DNS.

 

Option 1- Setup your DMARC policy with a simple, most common DMARC record. You will not receive any reports with this setup.

 

Host/Name: _dmarc

 

Value: v=DMARC1;p=none;

 

Option 2 - This setup will include reports. The DMARC Reports will be coming to the email you specify in ruf= and rua= parameters. If you do not wish to receive them anymore, remove these parameters (Similar to Option 1).

 

When you are no longer receiving negative reports, change your DMARC policy to quarantine which will not necessarily bounce email, but indicate to the recipient server they should consider quarantining it (junk or spam folder).

 

Host/Name: _dmarc

 

Value: v=DMARC1; p=quarantine; ruf=mailto:youremail@yourdomain.com; rua=mailto:youremail@yourdomain.com

 

ruf - Forensic (failure) reports

rua - Aggregate reports

​

​

​

​

​

​

6) Verify :

​

Go to your Settings >> Domains screen.
Add your domain (yourdomain.com). Click "Verify Domain".
Green check marks mean that the record has been added correctly.

 

Please note that new data input in a DNS zone of a domain can take up to 48h to propagate. It varies between hosting providers.