Browse Prior Art Database

Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1 (RFC7208) Disclosure Number: IPCOM000236452D
Original Publication Date: 2014-Apr-01
Included in the Prior Art Database: 2014-Apr-26

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Kitterman: AUTHOR


The current email infrastructure has the property that any host injecting mail into the system can use any DNS domain name it wants in each of the various identifiers specified by [RFC5321] and [RFC5322]. Although this feature is desirable in some circumstances, it is a major obstacle to reducing Unsolicited Bulk Email (UBE, aka spam). Furthermore, ADMDs (as described in [RFC5598]) are understandably concerned about the ease with which other entities can make use of their domain names, often with malicious intent.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 2% of the total text.

Internet Engineering Task Force (IETF)                      S. Kitterman Request for Comments: 7208                  Kitterman Technical Services Obsoletes: 4408                                               April 2014 Category: Standards Track ISSN: 2070-1721

                      Sender Policy Framework (SPF)            for Authorizing Use of Domains in Email, Version 1


   Email on the Internet can be forged in a number of ways.  In    particular, existing protocols place no restriction on what a sending    host can use as the "MAIL FROM" of a message or the domain given on    the SMTP HELO/EHLO commands.  This document describes version 1 of    the Sender Policy Framework (SPF) protocol, whereby ADministrative    Management Domains (ADMDs) can explicitly authorize the hosts that    are allowed to use their domain names, and a receiving host can check    such authorization.

   This document obsoletes RFC 4408.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

Kitterman                    Standards Track                    [Page 1]
 RFC 7208              Sender Policy Framework (SPF)           April 2014

 Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    ( in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF    Contributions published or made publicly available before November    10, 2008.  The person(s) controlling the copyright in some of this    material may not have granted the IETF Trust the right to allow    modifications of such material outside the IETF Standards Process.    Without obt...