emailengine VS apprise-api

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.

- [a web service (you host)](https://github.com/caronc/apprise-api) that can act as a sidecar. This solution allows you to keep your notification configuration in one place instead of across multiple servers (or within multiple programs). This one is for both Admins and Devs.

A lot of systems have already adapted to it such as HomeAssistant, Apache Airflow, ChangeDetection, Uptime Kuma and many others (<https://github.com/caronc/apprise/wiki/showcase#integrations>) which shows the commonality. Mailrise is an incredibly talented program that converts Emails sent to it to trigger notifications via Apprise.

*What else does it do?*

- Emoji Support (:rocket: -> ) built right into it!

One of the big features added is now the Apprise Web API can accept Attachments (all shapes and sizes) and then relay it to all of your endpoints. In the past you were limited to attachments only if you chose to use the CLI tool or write directly with the Apprise Python API.

Apprise is built into Home Assistant. You can centralize all of your configuration on a self serve web version of it and store all of your favorite endpoints there.

Oops forgot about that. Could host this and call it from node tho https://github.com/caronc/apprise-api

Looks like there is a server: https://github.com/caronc/apprise-api

So you can use the Apprise API from your app and have it trigger any number of notification services, configured in the Apprise config or web UI.

I just updated the (Apprise) API now. There was actually a bug with it and the new Apprise (v1.0.0) version (yikes!). This has been fixed now and I pushed a update to the API (v0.8.0) just now.

apprise-api - Apprise-api(https://github.com/caronc/apprise-api) Takes advantage of Apprise(https://github.com/caronc/apprise) through your network with a user-friendly API.