Build cloud backends with Infrastructure-from-Code (IfC), a revolutionary technique for generating and updating cloud infrastructure. Try IfC with AWS and Klotho now (Now open-source) Learn more →
Emailengine Alternatives
Similar projects and alternatives to emailengine
-
-
Klotho
AWS Cloud-aware infrastructure-from-code toolbox [NEW]. Build cloud backends with Infrastructure-from-Code (IfC), a revolutionary technique for generating and updating cloud infrastructure. Try IfC with AWS and Klotho now (Now open-source)
-
Postal
✉️ A fully featured open source mail delivery platform for incoming & outgoing e-mail
-
swagger-jsdoc
Generates swagger/openapi specification based on jsDoc comments and YAML files.
-
-
-
-
Appwrite
Appwrite - The Open Source Firebase alternative introduces iOS support . Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more!
-
-
apifire
Generates node.js express validators / routers / controllers in Typescript using an OpenAPI 3.0 spec
-
-
apprise-api
A lightweight REST framework that wraps the Apprise Notification Library
-
nvm
Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
-
-
-
-
-
routing-controllers
Create structured, declarative and beautifully organized class-based controllers with heavy decorators usage in Express / Koa using TypeScript and Routing Controllers Framework.
-
-
good_job
Multithreaded, Postgres-based, Active Job backend for Ruby on Rails.
-
foal
Full-featured Node.js framework, with no complexity. 🚀 Simple and easy to use, TypeScript-based and well-documented.
-
Sonar
Write Clean JavaScript Code. Always.. Sonar helps you commit clean code every time. With over 300 unique rules to find JavaScript bugs, code smells & vulnerabilities, Sonar finds the issues while you focus on the work.
emailengine reviews and mentions
-
Mike Perham of Sidekiq: “If you build something valuable, charge money for it.”
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.
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.
-
Poste.io – Complete Mail Server
https://github.com/postalsys/emailengine
Seems open-source to me.
-
Email: Explained from First Principles
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
-
Why is the JavaScript ecosystem like this
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.
-
Self-hosted email API for SMTP?
What about https://github.com/postalsys/emailengine ?
-
Do you use Swagger/OpenAPI to document your APIs? If so, what is your preferred way to generate the docs?
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.
-
redis vs. ioredis?
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.
-
Making Open Source economy more viable with dual license collectives
I use a similar model for EmailEngine (https://emailengine.app/). The code is dual-licensed under AGPL and a commercial license. The app has limited functionality by default - you can either buy a license key to activate it and use the app under the commercial license. Or fork the code, remove limitations (really easy to do, one or two lines of changes), and use it as AGPL. At first, I did not have that artificial limitation and no one was interested in buying the commercial license. Once I added that extra step, I got some customers.
-
Selling my own GPL software, part 1: a lot of hurdles
I’m selling an AGPL licensed app that allows to access IMAP/SMTP accounts over REST (https://emailengine.app). At first I sold it in a way where AGPL version was completely free and public, but you could pay to get the same thing with a MIT-license. Turned out that no-one cared about the license, everyone was happy to use the free AGPL thing, so I changed it in a way where the app is dual licensed under AGPL and proprietary license and you need a “license key” to fully unlock it. As it’s AGPL with source code available from Github you can freely remove that license key check, just a 1-line change. It’s still a big enough of a hurdle that I’ve actually gotten some customers.
-
A note from our sponsor - Klotho
klo.dev | 9 Jun 2023
Stats
postalsys/emailengine is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of emailengine is JavaScript.