email-oauth2-proxy VS syncthing-android

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

I use https://github.com/Catfriend1/syncthing-android which has an option to run only every X minutes of each hour, as a decent tradeoff.

This version also ships and Android Quick Settings tile that will start Syncthing for those X minutes and stop it outside of that schedule, so I'll hit the button as I'm putting on shoes to go out after making a shopping list on my phone or what have you

I built something on top of the Syncthing API this week after using it on its own for years.

A local instance of Syncthing can behave as a robust sync tool + inotify API for applications consuming the files: https://docs.syncthing.net/rest/events-get.html#get-rest-eve...

i believe there's an embeddable golang library, but if you want something easy to use on android check in on syncthing-fork which lets you define more granular sync conditions including "just turn on 5 minutes every hour" https://github.com/Catfriend1/syncthing-android

Sideloading this and setting this up via the web GUI is the best way for you to automatically sync files between devices. https://github.com/Catfriend1/syncthing-android/releases

Syncthing-Fork (version 1.27.0.1): File synchronization

You may find some information here: https://github.com/Catfriend1/syncthing-android/wiki/SD-card-write-access

If you're on Android, try Syncthing-Fork to save battery by running only a few minutes each hour

Syncthing fork is fine, download the github version under releases: https://github.com/Catfriend1/syncthing-android

Or there's Syncthing-Fork which I'm about to try (seems to be "better")