mailrise VS emailengine

Edit: Using AWS SES for now (PITA to setup though) and will setup https://github.com/YoRyan/mailrise as suggested below once I get my full systems back up. After the suggestions and testing, the hardest hurdle was having a VoIP number rather than regular Cell and using without a custom domain (and even different providers handle this differently). Using an email service seems to be one of the easiest methods to use, just have to make sure they allow SMTP access on the free tier. Hopefully the comments on this thread will help other in the future or give them alternative ideas. Thanks all!

I use mailrise which hosts a private SMTP gateway for Apprise notifications.

Link to the repo: https://github.com/YoRyan/mailrise

https://github.com/YoRyan/mailrise might be a decent option.

This project is similar to and inspired by Mailrise. I wanted a little more configuration than was supported by Mailrise, so decided to create my own option.

FYI, a similar system can be achieved with https://github.com/YoRyan/mailrise + https://github.com/caronc/apprise, but requires more setup

I ended up having to build mailrise from source so I could change it to use the nightly build of apprise instead of version 1.1 (which still had the bug). I actually just went back and tested that apprise 1.2 seems to be splitting both markdown and text messages properly for discord. I'll have to build an updated mailrise docker image and try again there. I'll file an issue if I run into problems.

When I started with https://emailengine.app, a similar product, I also considered releasing it as a SaaS. But looking at the competition, it seemed too complicated for me (just look at the compliance list for Nylas Email API https://www.nylas.com/security/#compliance ). Will be interesting to see how it works out for you. Good luck!

EmailEngine has all the code public [1], even though it is not open-source but is source-available. Some core parts I even published under the MIT license, like the IMAP client library I built from scratch to serve the special requirements EmailEngine has for IMAP access [2]

My thinking has always been that those who try to hack the license validation stuff and replace the missing build pipeline were never going to be my customers in the first place, so every second I would spend on them is a wasted effort.

[1] https://github.com/postalsys/emailengine

https://github.com/postalsys/emailengine

Seems open-source to me.

Well, I for one, hope that email stays as complicated as described in the post. Otherwise my project that simplifies access to email accounts (https://emailengine.app) would get no traction :D

I'd like to know if anyone here can share some experience using https://emailengine.app in a larger environment, e.g. managing / watching 100-200 email accounts and processing ~50.000-100.000 mails per day?

I had the same issues when I started with https://emailengine.app - just like Ghost, it’s an app written in Nodejs. I tried multiple distribution options at first and finally went with complete self containment. All modules are pre-installed during the publishing step and thus the user never needs to run npm. Or if you download the “compiled” single binary version you don’t even need node as it’s bundled with the binary (I use the pkg module to bundle these executables). So upgrading is just downloading and replacing the old version files with new ones.

The dowside - no sane way to use compiled dependencies, everything has to be vanilla javascript.