Why install Email OAuth2 Proxy with Web.Casa?
No manual Docker Compose needed. Web.Casa configures and starts everything.
Caddy auto-provisions SSL certificates. Reverse proxy works out of the box.
Monitoring, backups, updates, logs — manage all apps from one panel.
How to Install
Install Web.Casa first, then one-click install this app from the App Store.
Email OAuth 2.0 Proxy
Transparently add OAuth 2.0 support to IMAP/POP/SMTP client applications, scripts or any other email use-cases that don't support this authentication method.
Motivation and capabilities
Email services that support IMAP, POP and/or SMTP access are increasingly requiring the use of OAuth 2.0 to authenticate connections, but not all clients support this method.
This tool creates a simple local proxy that intercepts the traditional IMAP/POP/SMTP authentication commands and transparently replaces them with the appropriate SASL (X)OAuth 2.0 commands and credentials.
Your email client can continue to use the login or auth/authenticate options, with no need to make it aware of OAuth's existence.
The proxy works in the background with a menu bar/taskbar helper or as a headless system service, and is compatible with macOS, Windows and Linux.
Example use-cases
- You need to use an Office 365 email account, but don't get on with Outlook. The email client you like doesn't support OAuth 2.0, which became mandatory in January 2023.
- You used to use Gmail via IMAP/POP/SMTP with your raw account credentials (i.e., your real password), but cannot do this now that Google has disabled this method, and don't want to use an App Password (or cannot enable this option).
- You have an account already set up in an email client, and you need to switch it to OAuth 2.0 authentication. You can edit the server details, but the client forces you to delete and re-add the account to enable OAuth 2.0, and you don't want to do this.
- You have made your own script or application that sends or receives email, but it doesn't support OAuth 2.0, and you don't want to have to modify it to implement this.
- You work with multiple services or applications that use IMAP/POP/SMTP, and you don't want to have to set up OAuth 2.0 independently for each one.
In all of these cases and more, this proxy can help. Follow the instructions here to get started, and please open an issue with any problems or suggestions. For commercial support or feature requests, please also consider sponsoring this project.
FAQ
Can I install Email OAuth2 Proxy on Web.Casa?
Yes, Email OAuth2 Proxy is available in the Web.Casa App Store. You can install it with one click from the Web.Casa panel — no need to manually write Docker Compose files or configure reverse proxies.
How do I install Email OAuth2 Proxy on Web.Casa?
First install Web.Casa with curl -fsSL https://get.web.casa | bash, then search for "Email OAuth2 Proxy" in the App Store and click install. Web.Casa automatically configures the Docker container, assigns ports, and sets up a Caddy reverse proxy.
What is the default port for Email OAuth2 Proxy on Web.Casa?
The default port for Email OAuth2 Proxy on Web.Casa is 1999. You can bind it to a custom domain through Web.Casa's Caddy reverse proxy, which automatically provisions HTTPS certificates.
Does Email OAuth2 Proxy get automatic HTTPS after installation?
Yes. Web.Casa is built on Caddy, so after installing the app, simply bind a domain and Caddy will automatically provision and renew SSL certificates via Let's Encrypt — no manual configuration needed.
How do I back up Email OAuth2 Proxy data?
Web.Casa has a built-in backup plugin that supports automatic backups of Email OAuth2 Proxy data to local storage, S3, WebDAV, or SFTP. You can configure scheduled snapshots and retention policies to keep your data safe.
