emailengine

Here is a very similar project: https://emailengine.app/ Similar to Bichon, it also has a commercial license[1]: > EmailEngine is not free open-source software. It is "source available" software, meaning you can view and copy the source code, but you need a paid subscription[2] to run it beyond the free 14-day trial. Each EmailEngine instance comes with this trial, so you can test EmailEngine without any commitment. EmailEngine is based on ImapFlow[3], a modern and easy-to-use IMAP client library for Node.js that is MIT-licensed. [1] https://github.com/postalsys/emailengine/blob/master/LICENSE... [2] https://postalsys.com/plans [3] https://github.com/postalsys/imapflow

For anyone else wondering about the license, it's standard signing with an ec (sect239k1) key https://github.com/postalsys/emailengine/blob/master/lib/too... So the author can just write whatever validity date/license details (apparently hostname etc), sign it and give that to their customers.

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 [2] https://imapflow.com/

https://github.com/postalsys/emailengine Seems open-source to me.

Docker support is now enabled https://github.com/andris9/imapapi#docker

Although @sanity31415 has offered to get in touch with his 33mail product, there's also the option of standing up a REST API server in front of your mailboxes. There is an open source product called IMAP API which is available under 2 licenses depending on your needs: AGPL & MIT. It recently had its own Show HN [2]. [1] https://github.com/andris9/imapapi [2] https://news.ycombinator.com/item?id=25372987

Someone kind of provided a Docker container already but I haven't really looked into it as I don't use Docker so much https://github.com/andris9/imapapi/issues/28 If there are more requests for it then I'll probably add it to IMAP API.

XOAUTH2 is supported but all the heavy lifting about refreshing access tokens etc must be done on your application side. Whenever IMAP API requires an OAuth2 token it makes a HTTP request to an URL you have defined and whatever is returned from that URL is the used to authenticate against the IMAP server. Here's an example of such an authentication server: https://github.com/andris9/imapapi/blob/master/examples/auth... Basically you would have to run your own and configure IMAP API to requests tokens from that server.

I had similar issues where I wanted to remove IMAP complexity from client app, so I created a daemon proxy that sits between client and an IMAP server and “translates” REST API requests to IMAP commands: https://github.com/andris9/imapapi

If you just want a simple way to access your mail over HTTP (without the need for standards) you could probably also run imap-api[1] pointed at the Bridge. Although admittedly it does feel a bit hacky. Or maybe also getmail or fetchmail which will download your mail over IMAP and put it in the maildir format as files. [1] https://github.com/andris9/imapapi