Tiny SPF logo, depicts checking of envelope from
Here's what you need to do.
1: Publish your record.
2: Inform your users.
3: Use SPF for incoming mail.
FAQDownloadsSitemapContact Us
How it WorksNews What it Does ServicesForums
Publish a Record.

Publishing records is the first step to using SPF. Thousands of domains have already published, with more doing so daily.

If your organization:
- sends mail from under 5 servers,
- has a large technical staff, or
- isn't email-mission-critical,
Self-publishing is your best option,
with the quick and easy wizard.
ISPs, Inform Your Users.

If you know your users are well-behaved and always send mail through your servers, you don't need to do anything. (Law firms with their voluminous disclaimers should already be in this category. So should ISPs that provide SMTP AUTH.)

Otherwise, you should set up SMTP AUTH access for your users. Many ISPs already support this; yours may be one of them.

If you're a user, make sure that when you send mail it goes through your ISP's mail servers. You may need to enable Authenticated SMTP if you regularly connect to the Internet from outside your ISP's network.

We have prepared separate instructions for websites that generate email and for outsourced email service providers who send mail on contract.

Use SPF for incoming mail.

Many antispam and MTA vendors already include SPF support in their latest products. If you've been waiting for a reason to upgrade, now you have one!

If you prefer to install prepackaged opensource software, you should expect packages with SPF and SRS functionality already bundled in by September 2004.

If you are a technology enthusiast or early adopter comfortable with tweaking your mail server, go to the downloads page.

Home Services Media Contributors Sitemap Contact Us
Copyright © 2004-2006, licensed under the GFDL.