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