mox VS upspin

It's interesting how there is now

* Maddy: https://github.com/foxcpp/maddy

* Mox: https://github.com/mjl-/mox

* and Stalwart

which all see to aim for more or less the same niche. I wonder if we'll see two of those merge eventually.

Pitching my own: https://github.com/mjl-/mox has a "mox localserve" subcommand that runs a mail server on localhost for testing, including a pedantic mode and special addresses that cause failure conditions you may want to test for. This is actually a full mail server (SMTP, IMAP and much more) and it comes with a webmail client. The "localserve" mode was just so easy to implement that I couldn't resist.

Just run your own mail server on a Pi at home and get your ISP to set up a PTR record for you, assuming you are on a static IP. Mox is good and outputs all of the instructions for DNS etc.:

https://github.com/mjl-/mox

I have setup a mail server (thank you mox ) hosted on VPS in Linode and everything seems fine: no issue on SPF, DMARC, DKIM records, the reputation of the domain and of the IP is okay and the IP is not in any blacklist. Unfortunately, Google and MS are rejecting my emails, even if I added the DNS records that they asked to add in order validate my domain.

Super intriguing. Thanks for sharing!

It reminds me a bit of an early Go project called Upspin [1]. And also a bit of Solid [2]. Did you get any inspiration from them?

What excites me about your project is that you're addressing the elephant in the room when it comes to data sovereignty (~nobody wants to self-host a personal database but their personal devices aren't publicly accessible) in an elegant way.

By storing the data on my personal device and (presumably?) paying for a managed relay (and maybe an encrypted backup), I can keep my data in my physical possession, but I won't have to host anything on my own. Is that the idea?

https://upspin.io/

There are a few Go projects meant to be learned from:

- https://github.com/pion/opus for to learn audio

- https://github.com/benbjohnson/wtf for overall production quality

- https://github.com/upspin/upspin difficult to explain, personally I'm not a fan of the errors

You could also take a look at some real-world open-source projects. I like upspin for its idiomatic approach.

For example, Rob Pike's upspin places all its validations in the separate package. Do you agree with that approach? Which yet proven options there are?

Just a few projects that could perhaps interest you in terms of design of your own solution :

Upspin: https://upspin.io/

The early error wrapping work which emerged out of the Upspin project, that eventually made its way into the errors package, included stack traces in the wrap error. This would provide exactly what it appears you seek.