Author: askoorb
Description:
Your domain does not have an SPF record. This means that spammers can easily
send out E-mail that looks like it came from your domain, which can make your
domain look bad (if the recipient thinks you really sent it), and can cost you
money (when people complain to you, rather than the spammer). 01 Oct 2004 was
the target date for domains to have SPF records in place (Hotmail, for example,
started checking SPF records on 01 Oct 2004).
There is even an Extention for Mozilla Thunderbird! (http://taubz.for.net/code/spf/)
For more info see http://spf.pobox.com/forsysadmins.html
and http://spf.pobox.com/
A Wizard to help is at http://spf.pobox.com/wizard.html
To give an example of how it works:
In this example, AOL.com is the sending domain, and pobox.com is the receiver.
AOL publishes an SPF record, specifying which computers on the Internet can send
mail as user@aol.com
- When a real AOL user sends mail, pobox.com receives the message from an AOL
server.
- Pobox checks AOL's SPF record, to make sure the server is allowed to send
mail from AOL.
- The server is listed, so Pobox gives the message a pass.
(Expensive content-based spam checks can be bypassed, saving resources on the
receiver side.) 1. When a spammer forges mail from AOL, Pobox receives the
messages from an outside server.
- Pobox checks AOL's SPF record.
- The server is not listed, so Pobox gives the message a fail.
(Expensive content-based spam checks can be bypassed, saving resources on the
receiver side.)
Have fun,
Alex
Version: unspecified
Severity: enhancement
URL: http://spf.pobox.com/