crabmail

Static HTML email archive viewer in Rust
git clone git://git.alexwennerberg.com/crabmail
Log | Files | Refs | README | LICENSE

commit 9878a8a2e074ebbb0e1e72b2b3b2c526ba010119
parent cfa8283890f55d3c86019ee68b45c4c4677949ca
Author: alex wennerberg <alex@alexwennerberg.com>
Date:   Sun, 12 Dec 2021 10:01:07 -0800

restructure

Diffstat:
MREADME.md | 42+++++-------------------------------------
Acrabmail/README.md | 47+++++++++++++++++++++++++++++++++++++++++++++++
Rsrc/filters.rs -> crabmail/src/filters.rs | 0
Rsrc/main.rs -> crabmail/src/main.rs | 0
Rsrc/utils.rs -> crabmail/src/utils.rs | 0
5 files changed, 52 insertions(+), 37 deletions(-)

diff --git a/README.md b/README.md @@ -1,39 +1,7 @@ -# crabmail +# Crabmail -Simple, readonly mailing list archive. - -An html mail archive, written in Rust. Similar to [Hypermail](https://github.com/hypermail-project/hypermail). - -## Why? - -Despite decades of technological development, mailing lists persist as part of -the internet's infrastructure. Projects such as python, Go, postgresql, Linux, -etc, all rely on self-hosted mailing lists for their development. Mailing lists -are stable, persistent, and open to all. If you use a mailing list, you don't -have to worry about a platform closing, removing a key feature, or taking -actions that are against your values. Mailing lists are simple and based on -open standards, and email has enormous existing software infrastructure to -support it. Even in 2021, for many use cases, there exists no better -alternative to email and mailing lists. - -Unfortunately, mailing lists have fallen out of popularity, and many people are -trying to reinvent solutions to problems that mailing lists already solve. In -my view, the problem is that, in many cases, there aren't very many good, -modern options for mailing list software. Existing mailing list archives are -extremely old, largely unmaintained, and lack certain key features. More -"modern" mailing lists, like Discourse, are enormously complex and dificult to -self-host. Crabmail is built for simplicity, ease of hosting, and longevity. - - -THIS IS VERY EARLY IN DEVELOPMENT! - -Probably you don't want to work on this until it is more complete - -Ticket tracker until I can get it self hosted: - -[ticket tracker](https://todo.sr.ht/~aw/crabmail) - -mailing list until I get it self hosted: - -[mailing list](https://lists.sr.ht/~aw/hi) +Crabmail is a set of tools for self-hosting mailing list archives. Each tool can be used individually or in conjunction with others. +* Crabmail: A static HTML email viewer +* Crabmail-sync: A simple pull-based mbox sync +* Crabmail-admin: a web application for managing mailing lists diff --git a/crabmail/README.md b/crabmail/README.md @@ -0,0 +1,47 @@ +# crabmail + +Simple, readonly mailing list archive. + +An html mail archive, written in Rust. Similar to [Hypermail](https://github.com/hypermail-project/hypermail). + +## Design +Crabmail is built for simplicity, ease of hosting, and longevity. + +* Read-only: does not handle sending out emails, only displaying an archive. Updates to the archive can be followed via RSS. This greatly simplifies operational burden +* Static: ... +* Brutalist: Crabmail accepts email as-is, including its limitations, rather than trying to hide or obscure the underlying protocols + +## Why? + +Despite decades of technological development, mailing lists persist as part of +the internet's infrastructure. Projects such as python, Go, postgresql, Linux, +etc, all rely on self-hosted mailing lists for their development. Mailing lists +are stable, persistent, and open to all. If you use a mailing list, you don't +have to worry about a platform closing, removing a key feature, or taking +actions that are against your values. Mailing lists are simple and based on +open standards, and email has enormous existing software infrastructure to +support it. Even in 2021, for many use cases, there exists no better +alternative to email and mailing lists. And unfortunately, many communities +(and even institutions) have moved away from mailing lists and towards + +Unfortunately, mailing lists have fallen out of popularity, and many people are +trying to reinvent solutions to problems that mailing lists already solve. In +my view, the problem is that, in many cases, there aren't very many good, +modern options for mailing list software. Existing mailing list archives are +extremely old, largely unmaintained, and lack certain key features. More +"modern" mailing lists, like Discourse, are enormously complex and dificult to +self-host. + + +THIS IS VERY EARLY IN DEVELOPMENT! + +Probably you don't want to work on this until it is more complete + +Ticket tracker until I can get it self hosted: + +[ticket tracker](https://todo.sr.ht/~aw/crabmail) + +mailing list until I get it self hosted: + +[mailing list](https://lists.sr.ht/~aw/hi) + diff --git a/src/filters.rs b/crabmail/src/filters.rs diff --git a/src/main.rs b/crabmail/src/main.rs diff --git a/src/utils.rs b/crabmail/src/utils.rs