Mail-in-a-Box VS wildduck

may i recommend https://mailinabox.email ?

I don't see why we are a long way away. At the sandstorm end, we need to get to the point, where all updates (of both sandstorm and the apps) on the user machine are automatic. Much like they are automatic on various OSes (mobile OSes in particular but also MacOS/Windows). This is not impossible if a single OS like Debian-testing is targeted.

Mailinabox [1] almost does it. They target Ubuntu stable, and upgrades are mostly silent. But they needed user intervention when Ubuntu had to be upgraded from 18.10 to 22.04, which was quite challenging.

If sandstorm can get there, then putting it into a RPi box is simple. What's difficult is helping the general public understand the importance of protecting their data, so such a product has a reasonable market.

[1] https://mailinabox.email/

If you have a better solution, for example a good provider who offer agency packages which allows many domains and there is no catch, for example very small disk space, then hit me right away. Otherwise, please share your experience with hosting your own mail service. I found https://mailinabox.email/ and https://www.iredmail.org/ for example, but never had any experience with neither of them.

mailinabox.email works great on a basic vps.

Nodemailer author here. I now publish all my libraries/tools (like Nodemailer) under some permissive license (MIT, MIT-0, ISC). This gives the opportunity to use such a library without issues, and the end user never knows about these tools anyway. For example if I build a OSS software and commercial software that both use such library, then it is easier to manage it under permissive license - I don't want copyleft licenses turning up in my commercial software even if I'm the owner.

For OSS applications, I use EUPL (eg. https://wildduck.email/) or AGPL copyleft licenses. The license does not stop anyone using it as an application, but at the same time people are not free to copy, rename and sell it either.

- https://wildduck.email/ (E-mail)

Even though I have self-hosted things individually (eg: my Ghost blog on a RasPi connected to my home WiFi), something which I've always been concerned about is the separation of all these services, since they must have APIs and access rules. What's an ideal way of setting up a multi-service server like this, and what security policies should I implement. Additionally what are some must haves that you have running on your servers?

I understand self-hosting is a huge labour of love, and I have no qualms in investing time/effort learning :)

The largest WildDuck installation manages 100k+ email accounts with around 300TB of stored emails. So it does not always have to be one of the old and tried softwares. https://wildduck.email/

or install https://wildduck.email or mail in the box type of server, just host it yourself. Wildduck web interface allows you to make unlimited alias already.

I want to create an email service. I want to use MongoDB as a storage option. I want to store every email in a that DB but I can't find an email server technology that supports that. Are there any technologies that support that out there? As far as I could go only wildduck supports that but I don't like their documentation, setup, ecosystem, and more, so I'm looking for an alternative technology.

I use: https://github.com/nodemailer/wildduck for Mails.

I had noticed this/similar feature on wildduck mail server. Checkout the Advanced Security section there, might be what you are looking for.

WildDuck https://wildduck.email/