RFC 7293: The Require-Recipient-Valid-Since Header Field and SMTP Service Extension
In plain English — editorial summary, not part of the RFC
This document defines an extension for the Simple Mail Transfer Protocol (SMTP) called "RRVS" to provide a method for senders to indicate to receivers a point in time when the ownership of the target mailbox was known to the sender. This can be used to detect changes of mailbox ownership and thus prevent mail from being delivered to the wrong party. This document also defines a header field called "Require-Recipient-Valid-Since" that can be used to tunnel the request through servers that do not support the extension. The intended use of these facilities is on automatically generated messages, such as account statements or password change instructions, that might contain sensitive information, though it may also be useful in other applications.
Document record
- Document ID
- RFC7293
- Published
- July 2014
- Authors
- W. Mills; M. Kucherawy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5672RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- UpdateObsoleted
August 2009
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 9216S/MIME Example Keys and CertificatesCurrent
April 2022
- RFC 3281An Internet Attribute Certificate Profile for AuthorizationObsoleted
May 2002
- RFC 1281Guidelines for the Secure Operation of the InternetCurrent
November 1991
- RFC 7377IMAP4 Multimailbox SEARCH ExtensionCurrent
October 2014
- RFC 7489Domain-based Message Authentication, Reporting, and Conformance (DMARC)Obsoleted
March 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?