Sender Policy Framework: Authorizing Use of Domains in MAIL FROM
draft-lentczner-spf-00
| Document | Type |
Expired Internet-Draft
(individual in app area)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mark Lentczner , Meng Weng Wong | ||
| Last updated | 2005-05-26 (Latest revision 2004-10-13) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Experimental | ||
| Formats | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Ted Hardie | ||
| IESG note | |||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Mail on the Internet can be forged in a number of ways. In particular, existing protocols place no restriction in what a sending host can use as the reverse-path of a message. This document describes a protocol whereby a domain can explicitly authorize the hosts that are allowed to use its domain name in a reverse-path, and a way for receiving hosts to check such authorization.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)