Mailu VS email-oauth2-proxy

Consider installing Mailu instead, which is a single Docker container with a full mail server and Roundcube on top. Very easy to install.

I've been using Mailu (https://mailu.io/) for years and have had no problems. I love that it has the concept of domain admins so that people can manage mailboxes for their own domains. DNS isn't automatic, but meh. Upgrading is easy (Docker + automatic migrations).

Mailu is pretty solid for personal use and is lighter on memory than Mailcow

While hosting mail isn't easy, Mailu and similar projects make it way easier than it used to be.

Mailu on a cheap VPS: https://mailu.io

Mailu. It’s a docker image that has the whole email system pretty much all done for you. If you don’t know docker, learn it it’s well worth it.

So as the title says, I'm trying to set up a dockerized mailu server. I've done the docker compose setup from the mailu.io site, except it doesn't seem to work and I'm not exactly sure why. I'm guessing I'm just not entering in some information correctly, but I don't know for sure. One thing I know I'm not sure on is the db url and what exactly is it supposed to be. I don't remember the exact error I'm getting, as I'm not in front of my computer at the moment, but I do know it was the admin container that wasn't working properly. Either that or I don't have my DNS set up correctly.

What makes you say the protocol is different for each provider?

I maintain a proxy that transparently adds support for OAuth 2.0 support to IMAP/POP/SMTP clients (https://github.com/simonrob/email-oauth2-proxy), and for normal use it doesn’t need to know anything about which service it is connecting to. Apart from advanced features such as CCG or ROPCG which are mostly O365 only, what is different?

When it became clear many major email providers were going to require OAuth for IMAP/POP/SMTP access, I was pretty frustrated that I’d have to stop using clients/scripts that didn’t support this method.

Rather than spending lots of effort on migration, or switching clients entirely, I made a local proxy so that any IMAP (or POP/SMTP) client can be used with a “modern” email provider, regardless of whether it supports OAuth 2.0 natively: https://github.com/simonrob/email-oauth2-proxy. No need for your client to know about OAuth at all.

If you are not familiar with Email OAuth 2.0 Proxy by Simonrob, I would recommend you check it out. Star the repo or whatever you normally do. I wanted to acknowledge his repository because my work is built directly off what he maintains and creates.

https://github.com/simonrob/email-oauth2-proxy

"Just works" I run it with mbsync at the command line.

You do need a client id and some interaction with your O365 admin.

One potential solution I found is a proxy. Are you able to utilize an app password for this task?

You do still need details for an authorised client, but it’s possible to use those of one that’s already approved. See the readme section that explains this aspect: https://github.com/simonrob/email-oauth2-proxy#oauth-20-clie...

If you use this proxy of mine then any IMAP (or POP/SMTP) client can be used with a “modern” email provider, regardless of whether it supports OAuth 2.0 natively: https://github.com/simonrob/email-oauth2-proxy

maybe you can use https://github.com/simonrob/email-oauth2-proxy while you wait for official oauth2 support but I wonder why you are using another email server if you already have exchange online