News for hackers. Stuff that matters.
Re:Email is not broken: It’s a framework, not an application by ams6110 on Sunday April 15, 2012 @01:22PM (#3844123)
I agree with the entire sentiment as well, but would point out one flaw: You send a message and it either goes where it’s supposed to, or you get an error message back.

Generally yes, assuming everything between you and the recipient is properly configured, but it's not guaranteed. It's possible to send an email had it just disappears. No bounce, no delivery. It doesn't happen often, and as far as I know it's never happened to me, but there's nothing in the protocol that guarantees delivery or guarantees notification of delivery failure.

That said, this is not a big enough problem to require a new protocol or a change to the existing protocol, or in any other way be worth "fixing." If you are building something that requires guaranteed delivery of messages, don't build it on SMTP.

Re:Email is not broken: It’s a framework, not an application by gnaffle on Sunday April 15, 2012 @03:16PM (#3844401)
Nothing on the internet is guaranteed. Everything is at some point a leaky abstraction.

While it's possible for a mail to just disappear (or more often, automatically be sorted into a spam folder) the protocol is designed to be quite robust in how responsibilities for delivery are passed on to servers delivering the message.

Re:Email is not broken: It’s a framework, not an application by raintrees on Sunday April 15, 2012 @01:26PM (#3844133)
Doesn't this argue for a TCP-type implementation of "Did you get that or shall I resend?" ala Read Receipts? (On top of SMTP, that is...)