Haraka VS wildduck

postale.io has an MX record that points to mail.postale.io, which resolves to an AWS IP address (probably an EC2 instance) and has Haraka listening on port 25 (if its SMTP banner can be believed)

I found that Zerodha uses Haraka and Karan–their DevOps guy, mentioned it is easy-setup and performant.

The next time this happens i'll move to a self hosted solution, like haraka or anonaddy

Haraka Like: Simple to hook into the processing pipeline Dislike: Node.js and had some issues with stability when I last tried it

Having another SMTP as a choice is cool but not as fun as something that is way more configurable (ex. Haraka), or API driven (a la Postal).

Look at Haraka: http://haraka.github.io/

For the record, I'm using dovecot (https://www.dovecot.org/) for IMAP and Haraka (https://haraka.github.io/) for SMTP.

I run my own mail servers for small projects, though for my main email I've actually switched to ProtonMail.

It's never been easier to self host your email with projects like the following around:

- https://foxcpp.dev/maddy/

- https://github.com/albertito/chasquid

- https://github.com/haraka/haraka

Of course the usual dovecot + postfix setup is great for learning even if a bit complicated.

Haraka (https://haraka.github.io/) is a plugin-based mailserver written in JavaScript. I've messed with postfix before but found Haraka easier because instead of arcane configuration files I can just read, copy, and tweak a plugin to suit my needs. Policies for receiving, storing, forwarding, and ignoring mail can be arbitrarily complex.

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/