EmailEngine is an email client for apps. IMAP and SMTP are hard, so let EmailEngine handle these for you. Run REST API calls to interact with email servers and receive webhooks for changes on tracked email accounts.
With EmailEngine, you can focus on building features that matter instead of spending time rolling custom IMAP and SMTP connectivity logic.
Promote EmailEngine App. You can add any of these badges on your website.
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! - Source: Hacker News / about 1 year ago
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. - Source: Hacker News / almost 2 years ago
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. - Source: Hacker News / almost 2 years ago
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? Source: about 2 years ago
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... - Source: Hacker News / about 2 years ago
With EmailEngine you can both send and receive on behalf of your users using their own email accounts, so you wouldn’t need an extra service. Full disclosure - it’s my product. https://emailengine.app. Source: over 2 years ago
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. Source: over 2 years ago
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. Source: over 2 years ago
Gmail should still keep supporting App-Specific Passwords (requires 2FA to be enabled for that account) and if it's a single specific GSuite account (eg on your own domain, not gmail.com) then you could set up an "internal" OAuth application and authenticate via OAuth2 ("internal" applications do not require any validation). You can use both options when using something like EmailEngine (https://emailengine.app/). Source: almost 3 years ago
Worker threads can share data. Either by sharing SharedArrayBuffer or transferring ArrayBuffed values from one worker thread to another. That’s why I use worker threads instead of processes in https://emailengine.app. Source: about 3 years ago
Pkg does not include the source code but compiles it into V8 bytecode. I use pkg to build https://emailengine.app binaries and I’m quite happy with it. With compression the executable size comes down to about 40MB and for me this is good enough. Source: about 3 years ago
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... - Source: Hacker News / about 3 years ago
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... - Source: Hacker News / about 3 years ago
Do you know an article comparing EmailEngine App to other products?
Suggest a link to a post with product alternatives.
This is an informative page about EmailEngine App. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.