docker-mailserver VS wildduck

I have used Roundcube docker-compose-fpm.yaml, which looks like it can be easily extended with docker-mailserver

However... For a live fire, in production setup I would push people to use a meta package like docker-mailserver, mailcow, mail-in-a-box or modoboa as it's better to have someone else set the sane defaults to prevent you from missing that one line in you config.

Se proprio vuoi farlo per il gusto di riprendere familiarità con i vari concetti, giocherei con dei set di container docker tipo https://github.com/tomav/docker-mailserver (su GitHub ne trovi molti altri, alcuni tipo mailcow anche con GUI per gestire il grosso delle opzioni).

Yes, spam learning is documented on the Wiki.

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/