Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1
draft-kitterman-4408bis-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Scott Kitterman , Wayne Schlitt | ||
| Last updated | 2012-04-26 (Latest revision 2011-10-24) | ||
| Replaced by | draft-ietf-spfbis-4408bis, RFC 7208 | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
E-mail 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 reverse-path 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 a domain may explicitly authorize the hosts that are allowed to use its domain name, and a receiving host may check such authorization.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)