25:
406:
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
205:, 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.
228:
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:
182:, 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
328:) 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.
372:- 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
54:
350:- 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.
247:
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
291:
The various terms have different origins and sometimes different meanings, although these differences have often become moot on the modern internet.
338:
command, whose content is supposed to consist of the envelope sender address. Used in RFC 5321, RFC 3464, RFC 3834, Internet Mail
Architecture.
76:
163:
Ordinarily, the bounce address is not seen by email users and, without standardization of the name, it may cause confusion.
452:
427:
280:
264:
152:
208:
Only the envelope information is looked at to resolve where the email should go; the body of the email is not examined.
37:
47:
41:
33:
201:
information in the letter to be the same as the "envelope" values, such is not always the case. For example, on
90:
376:
information, while "2822-From:" refers to the address in the "From:" header seen by end users. Used in RFC 5598.
240:
It is typically not seen by users so it can be altered to include additional information without confusing them.
58:
344:- information that the SMTP protocol uses analogous to the envelope of a letter. Used in RFC 5230, RFC 5233.
432:
202:
268:
276:
244:
209:
108:
are delivered. There are many variants of the name, none of them used universally, including
422:
167:
388:- Another term that comes from the letter analogy for email. used in RFC 5321, RFC 3834.
447:
417:
299:
272:
105:
441:
356:- similar to envelope sender address, used in RFC 3461, RFC 3464, RFC 3834, RFC 4952.
190:
fields from the SMTP session - and neither of these is normally visible to the user.
101:
382:- Evolution of 2821-FROM as from October, 2008, SMTP has been defined in RFC 5321.
366:
command name. Used in RFC 5321, RFC 3464, RFC 3834, RFC 4408, RFC 4409, RFC 4952.
144:, etc. It is not uncommon for a single document to use several of these names.
395:
313:
320:
is created with the name "Return-Path:" containing the address on the
166:
If an email message is thought of as resembling a traditional paper
317:
237:
session, so a message can be rejected without receiving its body.
399:
325:
234:
147:
All of these names refer to the email address provided with the
89:"Return path" redirects here. For the term in electronics, see
18:
298:- When an email can not be delivered, the MTA will create a
216:
command to determine where the email should go, and the
402:
format. In this format, the email address from the
16:
Email address to which bounce messages are delivered
170:in an envelope, then the "header fields", such as
46:but its sources remain unclear because it lacks
263:Extended uses include mailing list handling in
362:- This variation comes directly from the SMTP
394:- When an email gets delivered to the user's
8:
312:- When the email is put in the recipient's
398:, one file format that may be used is the
324:command. Earlier forms of email (such as
77:Learn how and when to remove this message
302:and send it to the address given by the
220:command to indicate where it came from.
212:(MTA) using the SMTP protocol use the
7:
407:lines that begin with ">From ".
14:
193:While it is most common for the
23:
259:, etc.) or be missing entirely.
1:
428:Variable envelope return path
281:Bounce Address Tag Validation
265:Variable envelope return path
334:- the argument of the SMTP
469:
306:command. Used in RFC 4406.
88:
243:It is a required part of
233:It is given early in the
91:Return path (electronics)
203:electronic mailing lists
32:This article includes a
433:Sender Rewriting Scheme
354:envelope return address
348:envelope sender address
61:more precise citations.
159:Background information
453:Email authentication
269:email authentication
210:Mail Transfer Agents
245:Mail Transfer Agent
151:command during the
34:list of references
87:
86:
79:
460:
423:Email forwarding
405:
375:
365:
337:
323:
305:
258:
254:
250:
219:
215:
200:
196:
189:
185:
181:
177:
173:
150:
82:
75:
71:
68:
62:
57:this article by
48:inline citations
27:
26:
19:
468:
467:
463:
462:
461:
459:
458:
457:
438:
437:
414:
403:
373:
363:
335:
321:
303:
289:
256:
252:
248:
226:
217:
213:
198:
194:
187:
183:
179:
175:
171:
161:
148:
122:envelope sender
106:bounce messages
94:
83:
72:
66:
63:
52:
38:related reading
28:
24:
17:
12:
11:
5:
466:
464:
456:
455:
450:
440:
439:
436:
435:
430:
425:
420:
418:Bounce message
413:
410:
409:
408:
389:
386:return address
383:
377:
367:
357:
351:
345:
339:
329:
307:
300:bounce message
296:bounce address
288:
285:
273:spam filtering
261:
260:
241:
238:
225:
222:
160:
157:
134:return address
98:bounce address
85:
84:
42:external links
31:
29:
22:
15:
13:
10:
9:
6:
4:
3:
2:
465:
454:
451:
449:
446:
445:
443:
434:
431:
429:
426:
424:
421:
419:
416:
415:
411:
401:
397:
393:
390:
387:
384:
381:
378:
371:
368:
361:
358:
355:
352:
349:
346:
343:
342:envelope from
340:
333:
330:
327:
319:
315:
311:
308:
301:
297:
294:
293:
292:
286:
284:
282:
279:reduction in
278:
274:
270:
266:
246:
242:
239:
236:
232:
231:
230:
223:
221:
211:
206:
204:
191:
169:
164:
158:
156:
154:
145:
143:
139:
135:
131:
127:
123:
119:
118:envelope from
115:
111:
107:
103:
102:email address
99:
92:
81:
78:
70:
60:
56:
50:
49:
43:
39:
35:
30:
21:
20:
391:
385:
379:
369:
359:
353:
347:
341:
332:reverse path
331:
309:
295:
290:
262:
257:Resent-from:
227:
207:
192:
165:
162:
146:
141:
137:
133:
129:
125:
121:
117:
114:reverse path
113:
109:
97:
95:
73:
64:
53:Please help
45:
318:mail header
310:return path
287:Terminology
277:backscatter
110:return path
59:introducing
442:Categories
404:MAIL FROM
396:email box
380:5321-FROM
374:MAIL FROM
370:2821-FROM
364:MAIL FROM
360:MAIL FROM
336:MAIL FROM
322:MAIL FROM
314:email box
304:MAIL FROM
271:via SPF,
218:MAIL FROM
184:MAIL FROM
155:session.
149:MAIL FROM
142:Errors-to
130:5321-FROM
126:MAIL FROM
104:to which
67:June 2016
412:See also
316:, a new
267:(VERP),
180:Subject:
253:Sender:
214:RCPT TO
188:RCPT TO
55:improve
275:, and
178:, and
168:letter
100:is an
448:Email
392:From_
249:From:
224:Usage
199:From:
176:From:
138:From_
40:, or
400:mbox
326:UUCP
235:SMTP
197:and
186:and
153:SMTP
195:To:
172:To:
444::
283:.
255:,
251:,
174:,
140:,
136:,
132:,
128:,
124:,
120:,
116:,
112:,
96:A
44:,
36:,
93:.
80:)
74:(
69:)
65:(
51:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.