@@ -0,0 +1,29 @@
1++++
2+title = "Build an Email Toolchain for Urbit"
3+date = "2023-05-11"
4+
5+[taxonomies]
6+grant_type = ["RFP"]
7+grant_category = ["App Dev"]
8+
9+[extra]
10+image = ""
11+description = "Produce an Urbit-side client for sending E2EE email"
12+reward = "TBD"
13+assignee = [""]
14+champion = [""]
15+grant_id = "P1001"
16+completed = false
17+canceled = false
18++++
19+
20+Email is the glue for much of the legacy web. While many of us share an aversion to the proliferation of email, the ability to tie email to Urbit identity will enable users to unify their control over their digital life more than is currently possible.
21+
22+There are a lot of ways such a project could shake out.
23+
24+- The gold standard would basically be run-your-own-ProtonMail from Urbit.
25+- One could also build a CLI email agent, like [Mutt](http://www.mutt.org/). This would be a good start.
26+- Implementing [JMAP](https://en.wikipedia.org/wiki/JSON_Meta_Application_Protocol) should be feasible as well, and simpler than IMAP/SMTP.
27+- The minimum viable product would be a front-end on Mars for a connected email server process on Earth, including a full user story on how to operate this without too much tetchy sysadmin work required.
28+
29+Anything in between would also be acceptable. There are some interesting crossovers possible as well, such as sending email to `@p` or via the `user@sampel-palnet.arvo.network`.