|
Most domains send outbound mail through a relatively
small number of servers. Domains should describe that set
of servers in an SPF record in their DNS. Internet email
receivers can then reject forged messages which don't come
from an envelope sender domain's approved servers. This
wizard helps domain owners identify all the servers which
could be expected to send mail from their domain.
The SPF record:
v=spf1 ip4:87.124.0.0/15 include:aspmx.googlemail.com a:mail.notify-customer.com -all
can be explained as:
|
v=spf1 | This identifies the TXT record as an SPF string. |
|
ip4:87.124.0.0/15 |
Every host in the range 87.124.0.0-87.125.255.255 is allowed to send mail from petrolprices.com.
|
|
include:aspmx.googlemail.com |
Any server allowed to send mail from aspmx.googlemail.com is also allowed to send mail from petrolprices.com.
|
|
a:mail.notify-customer.com |
mail.notify-customer.com is also allowed to send mail from petrolprices.com.
|
|
-all |
No other servers are allowed to send mail from petrolprices.com.
This is a good default for sites particularly concerned about forgery.
|
You need to transfer these records to your DNS server by yourself. No
changes can be made by the wizard, it can only provide you with the
data that needs to be entered into your DNS server.
If you run BIND
Paste this into your zone file:
petrolprices.com. IN TXT "v=spf1 ip4:87.124.0.0/15 include:aspmx.googlemail.com a:mail.notify-customer.com -all"
|
If you run tinydns (djbdns)
'petrolprices.com:v=spf1 ip4\07287.124.0.0/15 include\072aspmx.googlemail.com a\072mail.notify-customer.com -all:3600
|
If you run Windows DNS
Please see these instructions.
More options
If your site requires more complex configuration than
this, you should read more about
mechanisms. You should also review the tradeoffs
involved in choosing an "all" default: see page 15 of the white
paper.
You can test some pretend scenarios at one of the DNS tools. MTAs that reject mail
because SPF tests failed will link to the why page.
|