Email explained from first principles

We’re Making Email More Modern With JMAP

The specifications for JMAP have been published by the Internet Engineering Task Force (IETF), marking a big victory for email tools now and in the future.

Documentation

Overview and quick start for the comail HTTP + SMTP send paths.

The Golden Age Of Open Protocols - AVC

Protocols are a geeky topic. It’s way more interesting to talk about applications. People will go on and on about why they like gmail or some other email application. But not a lot of people get excited about SMTP and IMAP which are the underlying email protocols that allow the gmail application to talk to […]

Use plain text email

There are two main types of emails on the internet: plain text and HTML. Many people, particularly in technical communities, strongly prefer or even require the use of plain text email from participants. However, your mail client may not have it set up by default. We'll help you get it configured, and introduce you to the norms and conventions of plain text email.

Mailing-List 2.0: Discourse

You got a few people working on something and you seek for an efficient way to communicate (ideas, news, messages, etc.) online. This guide gives you an overview about what you could expect in the past and what you should ask for nowadays. Mails According to Wikipedia, the first mail was sent in 1971. The access to a network we call Internet today was quite limited in these early days. Users have been mostly universities, and I guess, not everyone, but mostly the STEM disciplines Science, Technology, Engineering, and Mathematics. So it comes at no surprise that mails are perceived as inconvenient and antiquated.

How It All Started: Pre-W3C Web and Internet Background

1971: Ray Tomlinson of BBN creates email program to send messages across a distributed network.

better-email | sTeam Public

What i find interesting about this article is not the realization that MPI is like email, but the reverse, that human collaboration using messages is like MPI. The suggestion to use SMTP as a transport for things much more complex than emails is something worth looking at. It relates to my belief that the instant messaging difference does not come from the new protocols like XMPP for jabber, but from the new client interface that facilitates short messages in a conversational style. SMTP is equally (if not more) capable of transporting these messages. Sure, SMTP is not designed for "instant" messaging. but todays use of SMTP where my local SMTP server talks directly to your SMTP server, makes email is just as instant.

Home - maddy

Maddy Mail Server implements all functionality required to run a e-mail server. It can send messages via SMTP (works as MTA), accept messages via SMTP (works as MX) and store messages while providing access to them via IMAP. In addition to that it implements auxiliary protocols that are mandatory to keep email reasonably secure (DKIM, SPF, DMARC, DANE, MTA-STS).

The trouble with text-only email

Mozilla's manifesto commits the organization to a number of principles, including support for i [...]

Why kernel development still uses email

In a world full of fancy development tools and sites, the kernel project's dependence on email [...]

Super Mail Forward : an email that evolves as you forward it

Last year, Litmus held a community contest which theme was “Emails Worth Forwarding”. In order to participate, I created an email I called…

Email transparency

Many people have asked about how this email openness actually works. Is it really the case all our mail is copied to a list? If so, how do we avoid drowning in email?

Email and calendar made better

Fast, private email hosting for you or your business. More productive, lightning fast, simple and built to save you time.

Email and calendar made better

Fast, private email hosting for you or your business. More productive, lightning fast, simple and built to save you time.