This instructional article will demonstrate the SMTP.com configuration process of Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM) Signatures to ensure SMTP.com passes the DMARC alignment check and eliminate spam from your domain and increase security.
The SPF record identifies the mail servers and domains that are allowed to send email on behalf of your domain. The DKIM record, on the other hand, is a specially formatted DNS TXT record that stores the public key the receiving mail server will use to verify a message’s signature. These email authentication methods will be used to prove to ISPs and mail services that senders are truly authorized to send email from a particular domain and are a way of verifying your email sending server is sending emails through your domain.
The process of configuring SPF
In order to authenticate SMTP.com on SPF, please follow these steps:
- Login and head to your DNS Zone provider
- Create a new TXT record
- Input the DNS name as @ or your domain name
- Input the DNS value as v=spf1 include:_spf.smtp.com ~all
- Save the record
- Wait up to 72 hours to allow your DNS to process the changes
Screenshot below will show you an example of the SPF record. We’ll be using CloudFlare for this example.
Important Note: Each domain must have only one SPF TXT Record. If you have multiple SPF Records, SPF will return a PermError.
If you are using multiple IPs, ESPs, Third-Party services for your various email strategies, you should include them in a single SPF Record.
E.g v=spf1 ip4:18.57.156.221 include:_spf.smtp.com include:thirdpartyservice.com ~all
The process of configuring DKIM
In order to authenticate SMTP.com on DKIM, you need to add a custom DKIM key on your domain. Please contact their support team to provide your DKIM configuration.
Congratulations, you now successfully authenticated your outgoing mail stream from SMTP.com with SPF and DKIM.