RFC 4406: Sender ID: Authenticating E-Mail

In plain English — editorial summary, not part of the RFC

Internet mail suffers from the fact that much unwanted mail is sent using spoofed addresses -- "spoofed" in this case means that the address is used without the permission of the domain owner. This document describes a family of tests by which SMTP servers can determine whether an e-mail address in a received message was used with the permission of the owner of the domain contained in that e-mail address. This memo defines an Experimental Protocol for the Internet community.

Document record

Document ID

RFC4406

Published

April 2006

Authors

J. Lyon; M. Wong

Status

HISTORIC

Stream

IETF

Area

—

Pages

19

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC4406

Topics

• simple mail transfer protocol
• spam
• spoofing

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 4405SMTP Service Extension for Indicating the Responsible Submitter of an E-Mail MessageCurrent

  April 2006

• RFC 4871DomainKeys Identified Mail (DKIM) SignaturesObsoleted

  May 2007

• RFC 4408Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1Obsoleted

  April 2006

• RFC 4141SMTP and MIME Extensions for Content ConversionCurrent

  November 2005

• RFC 4130MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2)Current

  July 2005

• RFC 4865SMTP Submission Service Extension for Future Message ReleaseCurrent

  May 2007

• RFC 3885SMTP Service Extension for Message TrackingCurrent

  September 2004

• RFC 3865A No Soliciting Simple Mail Transfer Protocol (SMTP) Service ExtensionCurrent

  September 2004

Also filed under

• HISTORIC
• 2006
• IETF stream