Skip to content
IT security

Sender Policy Framework (SPF)

Updated

Sender Policy Framework (SPF) lets a domain publish which systems may send mail using an associated SMTP identity. A receiver compares the connecting source with that policy. SPF commonly checks the envelope-sender domain, which can differ from the From address a recipient sees; DMARC alignment helps connect those identities.

watch icon 2 min. read

What do I need to know about Sender Policy Framework (SPF)?

  • A domain should not publish multiple independent SPF policy records for the same identity. Legitimate sources must fit a coherent configuration.
  • SPF has DNS-lookup limits. Adding services through includes without reviewing the resulting chain can cause errors.
  • Forwarding can change the connecting source and affect SPF results.
  • An SPF pass does not inspect message content, approve a payment request, or independently validate the visible From address.

An illustrative example

A company adds a new support platform and appends another SPF record rather than updating the existing policy. Some recipients then see authentication errors. The administrator inventories the actual senders, corrects the published policy, and tests both ordinary employee mail and the support platform’s messages.

Practical checks

  • Identify all authorized sending systems for the relevant domain and follow each provider’s documented setup.
  • Validate the effective policy, including nested lookups, before publishing changes.
  • Inspect received test messages and monitor important mail routes after changes or provider migrations.

Five FAQs about Sender Policy Framework (SPF)

Is SPF the same as DKIM?

No. SPF checks whether the connecting source is authorized for an SMTP identity. DKIM validates a cryptographic message signature. DMARC can use aligned results from either.

Does SPF validate the address shown in my inbox?

Not by itself. The evaluated envelope identity can differ from the visible From domain. Alignment is a separate part of DMARC evaluation.

Can I publish two SPF records?

Multiple separate SPF policies for the same domain can produce an error. Build a valid combined policy with the necessary authorized sources rather than adding conflicting records.

Why can forwarded email fail SPF?

The forwarding server becomes the connecting source and may not be authorized by the original envelope domain’s policy. Evaluate the full route and other authentication results.

Should I add every service I recognize to SPF?

Only authorize systems that legitimately need to send using the relevant identity. Keep an owner and inventory so obsolete permissions do not accumulate.

Sources and further reading

IETF RFC 7208: Sender Policy Framework · Microsoft: Configuring SPF

Related terms

DKIM (DomainKeys Identified Mail) · DMARC · Email Authentication