After self-hosting my email for twenty-three years I have thrown in the towel

• Mail-in-a-Box

  183 13,286 8.8 Python

  Mail-in-a-Box helps individuals take back control of their email by defining a one-click, easy-to-deploy SMTP+everything else server: a mail server in a box.

  

There's alot that goes into a mail server stack, but it's no more complicated than k8s or other stacks these days.

For a pre-packaged mailserver environment, take a look at mailcow or mailinabox

https://mailcow.email

https://mailinabox.email/

There's a variety of ansible/chef/puppet up on github that can also be used to setup the invididual components

• os-tutorial

  40 26,324 2.3 C

  How to create an OS from scratch

Totally unrelated. But this guy has an amazing OS-from-scratch tutorial [0].

[0] https://github.com/cfenollosa/os-tutorial

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• Free-GPGMail

  4 530 4.0 Objective-C

  A modification of the Apple Mail plugin for GnuPG encrypted e-mails, so it does not require a support plan.

  

They might be talking about S/MIME.

I use https://github.com/Free-GPGMail/Free-GPGMail which is a plugin for GNUPG, without the "support" plan.

• hipp

  1 10 10.0

  Hamming Internet Payment Protocol

4. Add SMTP responses that mean "rejecting because your server sends spam" and "rejecting because that user sends spam". Servers can mark sent emails as "Receiver rejected this email" and inform the user.

5. Build a shared spam reporting system that accepts only signed emails and supports searching by email address. Receivers can use it to identify compromised user accounts and reject their email. Senders use it to identify receivers acting in bad faith (reporting ham as spam). A centralized version would be straightforward. A decentralized version would be a challenging project.

6. Add support to the SMTP protocol for reporting rate limits and cooling-off times to email senders. Admins of large shared email systems can feed these metrics into a monitoring system and receive alerts of problems early.

[0] https://github.com/mleonhard/hipp

Suggest a related project