Skip to main content
18 events
when toggle format what by license comment
Jun 10, 2017 at 19:22 audit First posts
Jun 10, 2017 at 19:22
Jun 10, 2017 at 17:07 audit First posts
Jun 10, 2017 at 17:07
Jun 5, 2017 at 12:05 audit First posts
Jun 5, 2017 at 12:05
May 19, 2017 at 6:27 audit First posts
May 19, 2017 at 6:27
May 17, 2017 at 4:09 comment added user @Mehrdad By envelope sender I mean the address that is used in the MAIL FROM command in the SMTP transaction and which is used as the return address by the mail server itself (most commonly in the case of needing to send a non-delivery notice after the SMTP transaction has finished). IIRC that address gets copied into a Return-Path header, but only during final delivery, so it wouldn't be there for example while a secondary mail exchanger is handling the message.
May 16, 2017 at 22:35 comment added user541686 By the way, I have to say I'm not actually sure what you mean by the "envelope sender". Are you talking about the Return-Path header? Because I've never seen that referred to as the "sender" header but maybe I'm just not familiar with that usage.
May 16, 2017 at 21:53 vote accept tuskiomi
May 16, 2017 at 10:41 comment added user @poizan42 RFC 5821 section 7.6: "the optional FOR clause should be supplied with caution or not at all when multiple recipients are involved" RFC 5821 section 4.4: "If the FOR clause appears, it MUST contain exactly one <path> entry, even when multiple RCPT commands have been given" ietf.org/rfc/rfc5321.txt
May 16, 2017 at 9:30 comment added poizan42 It may be worth noting that many mail severs injects a Received: entry into the headers that tells which recipient they received the message for. This header does not seem to have a standardized format though.
May 16, 2017 at 5:22 comment added Jonas Schäfer "For legitimate mail it usually is accurate enough" So this depends on what you call "accurate". As mentioned, classic mailing lists (e.g. Mailman based) operate by the same principle: they simply forward the email to the members of the list (+ some headers identifying the mailing list) without rewriting To and From headers (the distribution is handled on the SMTP envelope level only)—this is already "inaccurate" and "unwanted" to some and certainly breaks most DKIM signatures.
May 16, 2017 at 5:20 comment added Jonas Schäfer @SupremeGrandRuler Because the recipient information (in contrast to a possible Sender or Return-Path) is not contained in the email. Imagine the full recipient list was included, including the addresses the MUA got from the Bcc field (remember: SMTP (the envelope protocol) does not know about Bcc, it only knows about recipients) … That’d be a privacy issue (and a huge waste of space) not only on large mailing lists (operating by the same principle as Bcc does).
May 15, 2017 at 21:43 comment added user656011 @Michael What is the benefit of this? Why can't the email client display the "envelope"'s To/CC?
May 15, 2017 at 20:47 history edited user CC BY-SA 3.0
added 104 characters in body
May 15, 2017 at 20:44 comment added user541686 I was thinking of the Sender: header when I wrote that, and it was just an example. Just saying it'd be nice to add an example like this to your answer.
May 15, 2017 at 20:41 history edited user CC BY-SA 3.0
added 382 characters in body
May 15, 2017 at 20:37 comment added user @Mehrdad No; the (SMTP) envelope sender address is like the return address on the outside of the envelope (where it gets sent if it can't be delivered), whereas the address in the From header is whatever you write on the piece of paper that you stick inside the envelope and that the mailman doesn't even know about.
May 15, 2017 at 20:33 comment added user541686 I wish people made more real-world analogies here so others would understand what the physical equivalent is. The "sender" of an email is like the person handing the mailman the envelope; the "from" address is the one it's intended to be from. Like you could be a secretary sending on someone else's behalf, etc.
May 15, 2017 at 18:56 history answered user CC BY-SA 3.0