Browse Prior Art Database

The Require-Recipient-Valid-Since Header Field and SMTP Service Extension (RFC7293) Disclosure Number: IPCOM000237706D
Original Publication Date: 2014-Jul-01
Included in the Prior Art Database: 2014-Jul-04
Document File: 48 page(s) / 54K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

W. Mills: AUTHOR [+2]


Email addresses sometimes get reassigned to a different person. For example, employment changes at a company can cause an address used for an ex-employee to be assigned to a new employee, or a mail service provider (MSP) might expire an account and then let someone else register for the local-part that was previously used. Those who sent mail to the previous owner of an address might not know that it has been reassigned. This can lead to the sending of email to the correct address but the wrong recipient. This situation is of particular concern with transactional mail related to purchases, online accounts, and the like.

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

Internet Engineering Task Force (IETF)                          W. Mills Request for Comments: 7293                                   Yahoo! Inc. Category: Standards Track                                   M. Kucherawy ISSN: 2070-1721                                           Facebook, Inc.                                                                July 2014

              The Require-Recipient-Valid-Since Header Field                        and SMTP Service Extension


   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.

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

 Mills & Kucherawy            Standards Track                    [Page 1]
 RFC 7293              Require-Recipient-Valid-Since            July 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 Provis...