The Sender Policy Framework (SPF) is an open standard specifying a technical method to prevent sender address forgery. SPF is widely used as a primary practice in email sending to fight spam and authenticate the identity of email senders. SPF is a way to validate an email's FROM address against the server (the sending IP) that sent the email.
It is quite common to have messages blocked (i.e., not accepted for delivery) due to the message not being authenticated. Trying to send to a Gmail recipient using a FROM address domain that is not authorized to send from that IP? You can expect to be blocked.
Publishing SPF Records with JangoMail
To publish an SPF record, you simply need to add a TXT record to the Domain Name System (DNS) zone for the domain used in your FROM email address.
Condition 1:
If your FROM address domain is only used by JangoMail (Example: You have set up a custom subdomain, such as news.yourdomain.com specifically for use with your JangoMail account, which will not be used with your mail server or webserver)
Then use the following value for the TXT record for your FROM address's domain:
v=spf1 include:jangomail.com -all
Condition 2:
If your FROM address domain is used by JangoMail and by your organization (Example: You are using your existing email address assigned to you by your organization, such as FirstName.LastName@yourdomain.com)
If your domain administrator has not already published a SPF record for your organization's domain, he/she should do so immediately. The record should reflect the internal email server setup of your organization. To add JangoMail's network of IPs to the allowed list of senders for your domain, ADD (do not replace) the following value to your already existing SPF record:
include:jangomail.com
For example, if your FROM address is betty.joe@bakersdozen.com, and the SPF record for bakersdozen.com already exists as:
v=spf1 a mx -all
Then it should be modified to:
v=spf1 a mx include:jangomail.com -all
A message with great content does nothing if it doesn't reach the inbox! |
|
Comments
0 comments
Article is closed for comments.