Bounce address

<h2 id="background-information">Background information</h2>
<p>Ordinarily, the bounce address is not seen by email users and, without standardization of the name, it may cause confusion.  
</p><p>If an email message is thought of as resembling a traditional paper letter in an envelope, then the "header fields", such as To:, From:, and Subject:, along with the body of the message are analogous to the letterhead and body of a letter - and are normally all presented and visible to the user. However, the envelope in this analogy is the contents of the MAIL FROM and RCPT TO fields from the SMTP session - and neither of these is normally visible to the user.
</p><p>While it is most common for the To: and From: information in the letter to be the same as the "envelope" values, such is not always the case.  For example, on electronic mailing lists, the information seen in the "From:" header will come from the person who sent the email to the list, while the bounce address will be set to that of the mailing list software, so problems delivering the mailing list messages can be handled correctly. 
</p><p>Only the envelope information is looked at to resolve where the email should go; the body of the email is not examined.  Mail Transfer Agents (MTA) using the SMTP protocol use the RCPT TO command to determine where the email should go, and the MAIL FROM command to indicate where it came from.
</p>
<h2 id="usage">Usage</h2>
<p>While its original usage was to provide information about how to return bounce messages, since the late 1990s, other uses have come about.  These typically take advantage of properties of the bounce address, such as:
</p>
<ul><li>It is given early in the <a href="/facts/SMTP/TeCRKDpJ">SMTP</a> session, so a message can be rejected without receiving its body.</li>
<li>It is typically not seen by users so it can be altered to include additional information without confusing them.</li>
<li>It is a required part of <a href="/facts/Mail_Transfer_Agent/9SJG5sbb">Mail Transfer Agent</a> software, so it is easy for other programs to use.  In contrast, the "from" address in the body of the mail can be on several different headers (e.g. the From:, Sender:, Resent-from:, etc.) or be missing entirely.</li></ul>
<p>Extended uses include mailing list handling in <a href="/facts/Variable_envelope_return_path/1YN5UyJJ">Variable envelope return path</a> (VERP), <a href="/facts/Email_authentication/NWelESMa">email authentication</a> via SPF, <a href="/facts/Spam_filtering/WqhhDVXj">spam filtering</a>, and <a href="/facts/Backscatter_(email)/F8Ige6gF">backscatter</a> reduction in <a href="/facts/Bounce_Address_Tag_Validation/rKsVMmdE">Bounce Address Tag Validation</a>.
</p>
<h2 id="terminology">Terminology</h2>
<p>The various terms have different origins and sometimes different meanings, although these differences have often become moot on the modern internet. 
</p>
<ul><li>bounce address - When an email can not be delivered, the MTA will create a <a href="/facts/Bounce_message/vDJLbP2p">bounce message</a> and send it to the address given by the MAIL FROM command. Used in RFC 4406.</li>
<li>return path - When the email is put in the recipient's <a href="/facts/Email_box/C9Ghcvka">email box</a>, a new <a href="/facts/Email/6pD9GLtI">mail header</a> is created with the name "Return-Path:" containing the address on the MAIL FROM command.  Earlier forms of email (such as <a href="/facts/UUCP/dQ055F7b">UUCP</a>) would require information about each "hop" along the path that the email traveled to reach the destination, hence the "path" part of the name. Used in RFC 2821, RFC 3834, RFC 4409.</li>
<li>reverse path - the argument of the SMTP MAIL FROM command, whose content is supposed to consist of the envelope sender address. Used in RFC 5321, RFC 3464, RFC 3834, Internet Mail Architecture.</li>
<li>envelope from - information that the SMTP protocol uses analogous to the envelope of a letter.  Used in RFC 5230, RFC 5233.</li>
<li>envelope sender address - the mailbox address in a non-empty reverse path excluding any (deprecated) reverse routing info. Used in RFC 2821, RFC 3461, RFC 3464, RFC 3798, RFC 5228.</li>
<li>envelope return address - similar to envelope sender address, used in RFC 3461, RFC 3464, RFC 3834, RFC 4952.</li>
<li>MAIL FROM - This variation comes directly from the SMTP MAIL FROM command name. Used in RFC 5321, RFC 3464, RFC 3834, RFC 4408, RFC 4409, RFC 4952.</li>
<li>2821-FROM - Until October, 2008, SMTP was defined in RFC 2821, while the body of the email was defined in RFC 2822.  The term "2821-FROM" makes it clear that the address referred to is the MAIL FROM information, while "2822-From:" refers to the address in the "From:" header seen by end users. Used in RFC 5598.</li>
<li>5321-FROM - Evolution of 2821-FROM as from October, 2008, SMTP has been defined in RFC 5321.</li>
<li>return address - Another term that comes from the letter analogy for email. used in RFC 5321, RFC 3834.</li>
<li>From_ - When an email gets delivered to the user's <a href="/facts/Email_box/C9Ghcvka">email box</a>, one file format that may be used is the <a href="/facts/Mbox/r6eBSz0L">mbox</a> format.  In this format, the email address from the MAIL FROM command was placed on a line beginning with "From" followed by a single space, the "From_" term uses an underscore to represent the space to distinguish it from the "From:" mail header.   In this mailbox format, lines in the actual email that begin with a "From " have to be escaped and changed into lines that begin with ">From ".</li></ul>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Bounce_message/vDJLbP2p">Bounce message</a></li>
<li><a href="/facts/Email_forwarding/SndQNvXA">Email forwarding</a></li>
<li><a href="/facts/Variable_envelope_return_path/1YN5UyJJ">Variable envelope return path</a></li>
<li><a href="/facts/Sender_Rewriting_Scheme/IYA9zQTR">Sender Rewriting Scheme</a></li></ul>

Bounce address open-in-new

Bounce address