red-mail VS emailengine

These two are more user friendly alternatives for sending and receiving emails: - Red Mail - Red Box

Take a look at red-mail package.

Red-mail was appealing, but I was not pleased with the misleading error message when a connection failed. Nor was I pleased to see there are no log messages in the code.

It's the creator of Rocketry, Red Mail and Red Box again. This week I thought to make it easier to integrate command-line programs to your Python applications.

Some of you might know my other project, Red Mail, advanced email sender. This time I have quite a similar library to show, I just released a sister library for it: Red Box, the advanced email reader.

For example, you can send emails using built-in smtplib and email, but there is also Red Mail. Which provides you simpler interface.

I'm actually the author of Red Mail (email sending library) and Rocketry (Pythonic statement-based scheduler). I'm actually looking for example projects to create some practical tutorials of how one could use the libraries. Not sure which kind would be appealing to most and what kind of problems people have with alternative options (which I could address).

This can be easily achieved with Red Mail (for email sending), Red Bird (for handling the data in an abstract way) and Rocketry (for scheduling):

I have made a pretty handy SMTP sender for Python if the language is a bit familiar (the lib is extremely easy to use): https://github.com/Miksus/red-mail

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.