Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update spf-and-ip4-mechanisms.md #719

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update spf-and-ip4-mechanisms.md #719

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions content/docs/deliverability/spf-and-ip4-mechanisms.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,5 +13,3 @@ We recognize that SPF 7208 says the ptr mechanism **SHOULD NOT** be used, but it
**Note**: This mechanism is slow, it is not as reliable as other mechanisms in cases of DNS errors, and it places a large burden on the .arpa name servers.  If used, proper PTR records have to be in place for the domain's hosts and the "ptr" mechanism **SHOULD** be one of the last mechanisms checked.  After many years of SPF deployment experience, it has been concluded that it is unnecessary and more reliable alternatives should be used instead.  It is, however, still in use as part of the SPF protocol, so compliant check_host() implementations **MUST** support it.

We recognize that our SPF record does not pass muster with sites such as [dmarcian.com](http://dmarcian.com/), but rest assured that it does result in verdicts of pass on mail sent using the SPF record we publish.

You can also use our SPF tools for your SPF needs [SPF Inspector](https://tools.sparkpost.com/spf/inspector) and [SPF Builder](https://tools.sparkpost.com/spf/builder).