Stopped working with mbsync as local client side #380
Description
I know vague bug reports are very frustrating so I just want to observe this code didn't work on a clean install, run under uv to satisfy requirements. It hung at the auth phase and then started reporting invalid password/token.
IMAP server is O365 hosted on Microsoft. It hasn't changed afaik.
The client is mbsync (-from isync package) using gpg to decrypt the login password used for OAUTH2. I believe this set up attempts to use PLAIN. Confusing, but that's what it seemed to be negotiating across the TLS binding to office365. I don't have logs from the old set up, so it could be about the clean build of mbsync not tickling the right negotiation in the proxy to turn on OAUTH2.
This is after a 5 week Off-line hiatus, so it had no cached auth or refresh tokens. New mac (old one was wiped when I changed jobs)
Same client with cyrus-sasl2 mods works fine with mutt's oauth2.py code. Bootstrapped a secret store and with some gpg quirks continues to run. That uses XOAUTH2 validation.
Head osx version. Same uv instance for both to fix dependencies.
The .config file was identical, taken from a time machine backup.