How to minimize the amount of bounced emails?
How to minimize the amount of bounced emails from your campaigns? (SPF record)
To minimize the amount of the bounced emails from your campaigns, it is necessary to set up a SPF record on your sending domain.
What is SPF?
Sender Policy Framework (SPF) is a method of fighting spam. As more time passes, this protocol will be used as one of the standard methods of fighting spam on the Internet. An SPF record is a TXT record that is part of a domain’s DNS zone file. The TXT record specifies a list of authorized host names/IP addresses that mail can originate from for a given domain name. Once this entry is placed within the DNS zone, no further configuration is necessary to take advantage of servers that incorporate SPF checking into their anti-spam systems. This SPF record is added the same way as a regular A, MX, or CNAME record.
What is the SPF record that I need to install?
Here is the SPF record that you need to set up on your sending domain:
V=spf1 +A +Mx +Ip4:18.104.22.168 ~All
How to set up the SPF record on my domain? (ex.: GODADDY)
- Log into your Domain Management Account
- Go to Domains:
3. Next to the domain you want to manage, under the Action section, click on the Manage DNS button:
4. At the bottom of the Records section, click Add and select TXT from the menu.
5. Complete the following fields:
- Host – Enter the host name for the TXT record. For example, type @ to map the record directly to your domain name, or enter the subdomain of your host name (labeled Host), such as www or ftp.
- TXT Value – Enter the value you want to assign to the record.
- Select how long the server should cache the information. This is called TTL (Time to Live).
For a TXT SPF record, enter the SPF rule in the TXT Value field:
V=Spf1 +A +Mx +Ip4:22.214.171.124 ~All
6. Click Save to commit the changes.
The usage of public email domains like gmail.com, hotmail.com, yahoo.com, aol.com, etc leads to high numbers of bounces. Please use the proprietary domain names for emails like [email protected] VS [email protected]