5 ms·
Multiple implementations are a strength. In fact, you won't see a good replacement for SMTP without multiple independent implementations. (What will it look li
by dsr_ 14y ago
Multiple implementations are a strength. In fact, you won't see a good replacement for SMTP without multiple independent implementations.
(What will it look like? I would guess it will look like a two-part service, with one protocol for servers to talk to each other and another for clients to talk to servers. Servers will send tiny notifications to other servers that mail is available for their subscribers; then the receiving servers will retrieve the mail and cache it or store it for clients. This changes the spam problem fundamentally by requiring some persistence on the part of the sending server.)
- laumars 14y agoI would like to see the replacement of SMTP be designed along with a redesign of e-mails themselves as well. I'd like to see the HTML that is supported in e-mails standardised, so there's no more issues about which clients will render what. I'd like to see the failure notices standardised, so that invalid e-mail addresses produce a standard "404-like" response, and so on. The problem isn't so much that we have multiple implementations (I agree that can potentially be a strength). The problem is that there's very little that's consistent across the platforms.
- npsimons 14y agoI'd like to see the HTML that is supported in e-mails standardised Count me out. It wasn't even two weeks ago that we had the story here about how The Onion was hacked because somebody clicked on an obfuscated HTML URL in email.
- laumars 14y agoWhile we're at it, let's all abandon HTML5 and have every browser doing their own thing, because people occasional fall for fake anti-virus ads. </sarcasm> We can't stop social engineering like that - it's completely unavoidable. Which is why banks and payment providers regularly tell people not to follow links asking for bank details (etc). Yeah it sucks that The Onion got hacked that way, but your argument is doesn't fix that. Your argument is nothing more than cutting of your nose to spite your face (ie advocating an inconsistent platform for legitimate e-mails despite anchor tags working on every client already). At least if e-mail was completely redesigned, then we could have banks provide a unique cert that hangs in the e-mail header and can support the authenticity claim of the sender (I'm sure there's ways around that idea I've just presented - but that was just off the top of my head. Any such design would obviously need to be thoroughly thought out)
- raylu 14y agoI think he's saying we should instead have text-only e-mail, because that's both standard and has a tiny attack surface.
- laumars 14y agoThat doesn't fix anything either. Many clients make URLs clickable (even with text-only emails) and even if those clients didn't do that, someone will just copy and paste a URL into the address bar without looking. Given that the average user isn't an expert on domain names, it's not actually that hard to trick them into thinking that face.book.com isn't the same as facebook.com (and even those that are savvy enough to know the difference might misread the link and get fooled occasionally). So like I said before, it's impossible to prevent social engineering.
- raylu 14y agoIt's impossible to prevent all cases of social engineering with a purely technical solution, this is true. But that doesn't mean that we should disregard how much easier phishing attacks are with the advent of HTML mail. The goal here is not so much to stop social engineering dead in its tracks as to prevent some of the low-effort attacks that do happen.
- laumars 14y agoBut again, I refer you to my HTML5 example. Should we dumb down what websites are capable of rendering to prevent social engineering via the web? What you're proposing is making things harder to work in the hope that human intelligence will prevail. But the problem is that these cases are where human intelligence has failed, so making things harder is just counter productive. And this is why you can't prevent social engineering from happening and why crippling technology and creating a worse user experience just to try catch a few fringe cases is just a backwards approach to handling the issue. Instead what we need is methods in place to verify the authenticity of senders and better education to users so that don't make silly mistakes like installing random "virus scanners" from web ads or clicking strange URLs in e-mails (and the URLs themselves could be standardised. eg no sub-domains become clickable, to prevent people falling for face.book.com).
- jackinloadup 14y agoI wonder if this could be fixed by displaying SSL certificate status next to email titles. Much like browsers do for websites. This way before you open or at least before you click anything in the email you can see the validity of the sender.
- pyre 14y agoYou can't put the genie back in the bottle, unfortunately. Most people use clients that support HTML right now, and a new format that doesn't support some sort of rich text decoration (like HTML) isn't going to become popular enough to matter.
- loup-vaillant 14y agoA ridiculously cheap and powerful alternative to HTML (or any other static format for that matter), would be a bytecode format intended to be executed in a sandboxed virtual machine. Possibly something like Flash. That should give you all the bells and whistles you could possibly want with a document format. Now, there still are some loose ends about various screen sizes, preferred font family and size, and of course allowing textual searches, but those parameters should be few enough to be less problematic that HTML is right now.
- pyre 14y agoReally? Flash is more secure than HTML? Maybe we should just embed Java applets in emails? This still doesn't solve the "click a link that takes them elsewhere" issue that was brought up.
- loup-vaillant 14y agoI did say "sandboxed", did I not? Just have your VM refuse to download anything before you click somewhere, and let it compute the relevant URL so it can show it to you the way Firefox does. If this is too harsh, then relax the restriction to only download to, say, the domain name of the current main URL. If this is still too harsh, then have a NoScript like button to relax restrictions manually, on a case by case basis. It would disable any form of cross scripting by default, which in my opinion is a better state of affairs than HTML alone is right now (now, you can embed an external image in a web page, and bam, Facebook knows what you read).
- marssaxman 14y agoI'd like to see it standardized that HTML is not supported in e-mails. Email worked fine before HTML came along and all the good email is still HTML-free... in my experience, only robots use HTML.
- laumars 14y agoWhile the vast majority of my correspondence is plain text formatted. I do think there's a place for markup. Something that can embed images, provide different formatting styling (bold, italics, underline, colours and perhaps even sizes). It's also nice having an option between serif, sans serif and monospaced typefaces. Then there's hyperlinks. If not like HTML anchor tags were the hypertext is independent to the destination, but still some method to follow links in e-mails as a lot of online registration requires email activation that way. So do think there is a benefit for some level of markup in e-mails.
- wtbob 14y ago> Then there's hyperlinks. If not like HTML anchor tags were the hypertext is independent to the destination, but still some method to follow links in e-mails as a lot of online registration requires email activation that way. Well, there's the (IIRC) RFC-specified way to write URLs within '<URL:' and '>' pairs, e.g. <URL:https://news.ycombinator.com/> https://news.ycombinator.com/> (interestingly, the HN URL-finder doesn't support that).
- laumars 14y agoThere's a million different ways it can be done. I only suggest a HTML-derived format because of familiarity.
- smnrchrds 14y agoPlain text works fine in ASCII world. But if you ever need to read bi-directional emails like I did(e.g. Arabic text with some English words) you will understand the necessity of using HTML in email. Without proper formatting and markup that HTML offers, English words seem to fly around the text and end up at semi-random places. I wish to see better support for non-ASCII plain text in email clients and web browsers, but until the HTML is all I have.
- EvilLook 14y ago>What will it look like? I would guess it will look like a two-part service, with one protocol for servers to talk to each other and another for clients to talk to servers. So SMTP and POP3/IMAP? >Servers will send tiny notifications to other servers that mail is available for their subscribers; then the receiving servers will retrieve the mail and cache it or store it for clients. This changes the spam problem fundamentally by requiring some persistence on the part of the sending server. So NNTP?
- pyre 14y ago| So SMTP and POP3/IMAP? I think that the 'clients to talk to servers' part is referring to sending email, unless you think the webmail is the only way to send email. POP/IMAP are for reading email from the receiving server, not for sending out new emails. | So NNTP? I was under the impression that most Usenet networks used UUCP.
- ethomson 14y ago> POP/IMAP are for reading email from the receiving server, not for sending out new emails. They probably shouldn't be, though, there's an IMAP extension for submission. > I was under the impression that most Usenet networks used UUCP. No, NNTP. UUCP hasn't been used seriously for over a decade. Yours, news.ycombinator.com!ethomson
- pyre 14y ago| No, NNTP. UUCP hasn't been used seriously for | over a decade. Looked it up and it seems you are mostly[1] right. Some time ago, I picked up the notion that most large Usenet networks synced articles between each other using UUCP, but clients used NNTP to pull down articles for reading. Not being a very avid Usenet user, I just took this at face value (also not knowing much about UUCP, like the fact that it used Layer 1 or Layer 2 protocol prior to TCP/IP). [1] According to Wikipedia, UUCP was still in use in 2006 for at least one software product.
- 14y ago
- saraid216 14y agoHow come I didn't see this stuff come up when Google was all, "We are going to replace email with Wave!"