Forced Redirects in SMTP
draft-sam-smtp-redirects-00

Document Type Active Internet-Draft (individual)
Last updated 2020-07-09
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                   E. Sam
Internet-Draft                                               9 July 2020
Updates: 5321 (if approved)                                             
Intended status: Standards Track                                        
Expires: 10 January 2021

                        Forced Redirects in SMTP
                      draft-sam-smtp-redirects-00

Abstract

   This document specifies two new response codes in the SMTP protocol
   that relate to the redirection of emails meant for one email address
   to another mail server/email address.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 10 January 2021.

Copyright Notice

   Copyright (c) 2020 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 (https://trustee.ietf.org/
   license-info) 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 Provisions and are
   provided without warranty as described in the Simplified BSD License.

Sam                      Expires 10 January 2021                [Page 1]
Internet-Draft          Forced Redirects in SMTP               July 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Problems with using 551 response code . . . . . . . . . . . .   3
   3.  The 557 and 558 response codes  . . . . . . . . . . . . . . .   3
     3.1.  The 557/X.2.7 Response Code . . . . . . . . . . . . . . .   4
     3.2.  The 558/X.2.8 Response Code . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   In todays digital world, email is the primary way of communication
   for almost all Internet users.  On the internet, there are many
   services and accounts that require the use of a email address for
   password recovery, etc.  Changing a email address while "letting go"
   of the old one can be very difficult.  For the most part there
   already is a solution: People trying to switch from one provider to
   another have to "forward" email from their old mailbox to their new
   one.

   This system presents some problems.  First off, the forwarded emails
   are still going through the original mail server. w `While some may
   like the system of silent fowarding (for example; having a support
   email that goes to a random employee in the support department), some
   may want to directly give their new address to people sending them
   mail.  If someone switched their email address to prevent their
   emails from being processed or "seen" by the original mail server,
   forwarding would be insufficient.  In addition, mail server admins
   may not want to deal with the extra bandwidth/CPU time required to
   forward/relay emails to another server.  The 2nd problem is that the
   new email address doesn't automatically get updated with all of the
   accounts or internet services the owner of the email address may
   have, meaning that many entities wouldn't have any record of the new
   email and would continue to send emails to the old email.  Changing
   the email address for each service a person has signed up with is
   nearly impossible, and there are bound to be some that a person would
   forget to change.  To remedy this some opt to send an automated reply
   email with their new email address to anyone that emails them; but
   this system is not standardized and most automated systems fail to
   recognize a email like this.  This document aims to fix these
Show full document text