emailengine VS routing-controllers

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

Oh, yeah, I forgot my pitch. The link is https://emailengine.app - EnailEngine acts as a mail client, basically the same way Thunderbird runs on desktop, or the iPhone Mail on phone, but instead of a GUI it has REST API and instead of desktop notifications it sends JSON webhooks. And instead of a single email account, it can manage thousands of accounts.

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 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.

What about https://github.com/postalsys/emailengine ?

For https://emailengine.app I generate swagger docs with the hapi-swagger plugin https://github.com/hapi-swagger/hapi-swagger - the process is pretty much fully automatic as it uses the input and output schema validations.

I use ioredis in https://emailengine.app and it works very well. Haven’t used the redis module for a long time so can’t compare but I like easily I can set up error retries etc with ioredis. I’ve also used it with Redis Sentinel.

The standard is express. I say that with some glibness, but its the only true answer: a ton of the other higher level frameworks and pluggable middlewares still rely on the core express Request/Response types. And there are a ton of higher level frameworks, if the number of distinct replies wasn't obvious.

I really like express + routing-controllers [1], if you're on typescript.

[1] https://github.com/typestack/routing-controllers

I currently use https://github.com/typestack/routing-controllers and https://github.com/epiphone/routing-controllers-openapi with https://github.com/Redocly/redoc

If I don’t want to use nest then I would use express or koa with routing-controllers. Using this package you can write controllers with classes and decorators which is similar to nest js. There are a lot of other features too.