neutron VS wildduck

PS: I hope that we selfhosters will have a modern, efficient, easy to use mail suite one day with modern features like JMAP, good self-learning spam integration, automated checks and validations for SPF/DMARC/DKIM or whether the IP/host suddenly appears in a blocklist and integrated encryption at rest for emails. Something that isn't 30 services in a container image, with 30 different configuration styles. Maybe even with an API integrated that's compatible to the ProtonMail frontend (like the neutron server once intended to be). Anyway, I'm sorry for dreaming. ;)

A bit related: there was a FOSS backend once but I don't think anyone wants to push further.

Some folks once started neutron which is an email server that can be used with the FOSS Protonmail web client but it was abandoned. And I guess you'd want to support JMAP in addition to IMAP as well apart from having automated encryption of incoming plain-text emails.

Anyway, to the topic: there was once neutron which is a server that aimed at ProtonMail compatibility. So that'd would simply would be able to use the same open source frontend from ProtonMail. However, this was abandoned. So you, or somebody else, could revive it.

Some folks also started implementing an FOSS ProtonMail but this project was abandoned at some point. But maybe someone will fork and revive it one day.

Two devs once started implementing a free ProtonMail server but they abandoned it. It's understandable, since it's a lot of work.

Some folks once started a free implementation of the Protonmail backend in Go. Maybe you want to revive it?

Some folks also started an open source Protonmail backend but this was abandoned at one point.

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/