What is SPF? Sender Policy Framework explained simply

SPF (Sender Policy Framework) is a DNS record that lists the servers allowed to send mail for a domain. Receiving servers check it to see whether the sending server is authorized.

How it works

The domain owner publishes one TXT record that starts with "v=spf1". When mail arrives, the receiving server looks up that record and checks whether the connecting server is on the list.

SPF checks the envelope sender (the MAIL FROM and HELO identities used during delivery). It does not check the From address that people see in their inbox.

pass: the server is authorized
fail: the server is not authorized
softfail: probably not authorized (a weak policy)
neutral / none: no assertion, or no record
temperror / permerror: a temporary DNS error, or a broken record

Why it matters for newsletters

Google requires every sender to set up SPF or DKIM. Senders of more than 5,000 messages a day to Gmail accounts need both. Yahoo also requires bulk senders to use both.

SPF alone does not stop someone from faking your From address. DMARC adds that link, so SPF is usually paired with DKIM and DMARC.

Things to check

Publish only one SPF record per domain.
Mechanisms that trigger DNS lookups, such as include, are limited to 10 per check. Going over returns permerror.
When you add a new sending service, check whether it needs to be included in your SPF record.

How Newsletter Ready handles this

Newsletter Ready sends from its own domain with DKIM signing, and the domain has SPF and DMARC records in place.

Each issue is drafted by AI from your website articles. Nothing is sent until you approve it.

See a sample issue made from your website Email domain checker (SPF, DKIM, DMARC) →What is DKIM? →What is DMARC? →

Email newsletter glossary

Sources

This page is general information, not legal advice.