Timeline for How did I get this email without a "To" field?
Current License: CC BY-SA 4.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Feb 11 at 22:44 | history | edited | thomasrutter | CC BY-SA 4.0 |
added 3 characters in body
|
Dec 4, 2022 at 23:45 | history | edited | thomasrutter | CC BY-SA 4.0 |
added 304 characters in body
|
Apr 27, 2021 at 21:51 | history | edited | thomasrutter | CC BY-SA 4.0 |
added 61 characters in body
|
Jan 21, 2018 at 22:34 | history | edited | thomasrutter | CC BY-SA 3.0 |
added 2 characters in body
|
Jan 19, 2018 at 15:52 | comment | added | mattdm | Probably worth noting that when you say "newer versions of the protocol", that means "newer than 1995". | |
Jan 19, 2018 at 15:37 | comment | added | Johannes Kuhn |
@TobySpeight This is only true if there is only one RCPT-TO .
|
|
Jan 18, 2018 at 11:32 | comment | added | Toby Speight |
Perhaps worth mentioning that some MTAs will include a for clause in their Received: headers, showing the envelope RCPT TO on that hop. I haven't checked, but I expect that this is done only when there's a single recipient (for privacy); there don't seem to be any such for clauses in the question's headers.
|
|
Jan 18, 2018 at 7:51 | comment | added | Nelson | @HopefullyHelpful it's not baffling. It is extremely difficult to change such an old standard and not outright break almost everything that uses it. SMTP made assumptions about users being scientists. The end users were the security. The internet was not designed at all as a consumer service. Not even close. | |
Jan 18, 2018 at 4:58 | comment | added | HopefullyHelpful | It's still baffling that after all theses years noone bothered to implement a more secure standard | |
Jan 17, 2018 at 23:41 | history | edited | thomasrutter | CC BY-SA 3.0 |
added 198 characters in body
|
Jan 17, 2018 at 4:53 | history | edited | thomasrutter | CC BY-SA 3.0 |
added 1235 characters in body
|
Jan 17, 2018 at 4:41 | history | answered | thomasrutter | CC BY-SA 3.0 |