{"id":903,"date":"2011-11-27T20:03:49","date_gmt":"2011-11-27T19:03:49","guid":{"rendered":"http:\/\/cerezo.name\/blog\/?p=903"},"modified":"2024-10-14T14:08:54","modified_gmt":"2024-10-14T12:08:54","slug":"the-genesis-of-e-mail","status":"publish","type":"post","link":"https:\/\/cerezo.name\/blog\/2011\/11\/27\/the-genesis-of-e-mail\/","title":{"rendered":"The Genesis of E\u2011mail"},"content":{"rendered":"<p style=\"text-align: justify;\">Every time an email is sent, it\u2019s expected to be handled to its recipient, no matter what their service provider is. But in the first days, it wasn\u2019t so simple: early commercial email services (CompuServe, Prodigy, Delphi, \u2026) featured proprietary email services with no concept of an universal e\u2011mail address, which in turn created technical barriers that originated the commercial practice of settling charges for email delivery between service providers. In other words, there were interconnection agreements which detailed the delivery charges between providers, bounding the two parties to periodically settle their accounting differences, much like in the other telecommunication networks (telex, fax, teletex, <span class=\"caps\">SMS<\/span> and phone termination fees).<\/p>\n<p style=\"text-align: justify;\">But the number of said required agreements grew exponentially as the number of service providers expanded, and so did the technical difficulties to integrate their different email services. <a href=\"http:\/\/en.wikipedia.org\/wiki\/X.400\" target=\"_blank\" rel=\"noopener\">X.400<\/a> was born to solve these issues, implicitly providing support to keep settlement scores between carriers and their multi-interface delivery technology (vg. the <strong>preferredDeliveryMethod <\/strong>attribute). In the end, X.400 didn\u2019t really take off and was substituted in 1990 by the much simpler X.500 protocol: but not due to its tremendous complexity, but rather due to the decisive move of service providers to stop settling accounts between them so they could just use X.500 to interconnect their directory services.<\/p>\n<p style=\"text-align: justify;\">As usual, it\u2019s almost never about technology, which can be better thought as the child of necessity and will. The hassle of reaching agreements was getting so high with the growing number of service providers that their diminishing return stopped justifying the related bargaining costs, which in turn were precluding the emergence of the essential network effects from the growing number of email users (as per <a href=\"http:\/\/en.wikipedia.org\/wiki\/Metcalfe%27s_Law\" target=\"_blank\" rel=\"noopener\">Metcalfe<\/a>-<a href=\"http:\/\/en.wikipedia.org\/wiki\/Beckstrom%27s_law\" target=\"_blank\" rel=\"noopener\">Beckstrom<\/a>-<a href=\"http:\/\/en.wikipedia.org\/wiki\/Reed%27s_law\" target=\"_blank\" rel=\"noopener\">Reed<\/a>\u2019s Laws): that is, they were the real <a href=\"http:\/\/en.wikipedia.org\/wiki\/Limiting_factor\" target=\"_blank\" rel=\"noopener\">limiting factor<\/a> blocking the growth of the early Internet. Nowadays, the only trace of these agreements survives in <a href=\"http:\/\/en.wikipedia.org\/wiki\/Internet_transit\" target=\"_blank\" rel=\"noopener\">transit traffic agreements<\/a>, in turn solved by <a href=\"http:\/\/en.wikipedia.org\/wiki\/Peering\" target=\"_blank\" rel=\"noopener\">peering agreements<\/a>.<\/p>\n<p style=\"text-align: justify;\">To sum up, notice the circular paradox that the history of email established, a curious tale of unintended consequences: free email begot spam, and spam beget the obvious solution to <a href=\"http:\/\/en.wikipedia.org\/wiki\/Cost-based_anti-spam_systems\" target=\"_blank\" rel=\"noopener\">start charging for email to put an end on it<\/a>. Whether the trade-off was correctly solved depends on whom you talk&nbsp;to.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Every time an email is sent, it\u2019s expected to be handled to its recipient, no matter what their service provider is. But in the first days, it wasn\u2019t so simple: early commercial email services (CompuServe, Prodigy, Delphi, \u2026) featured proprietary email services with no concept of an universal e\u2011mail address, which in turn created technical&nbsp;[\u2026]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"wp_typography_post_enhancements_disabled":false,"ngg_post_thumbnail":0},"categories":[13],"tags":[],"_links":{"self":[{"href":"https:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/posts\/903"}],"collection":[{"href":"https:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/comments?post=903"}],"version-history":[{"count":4,"href":"https:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/posts\/903\/revisions"}],"predecessor-version":[{"id":1618,"href":"https:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/posts\/903\/revisions\/1618"}],"wp:attachment":[{"href":"https:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/media?parent=903"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/categories?post=903"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/tags?post=903"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}