Open sevalsixarci opened 4 days ago
Sorry for the delay. Does the error displays straight, or after a delay? Do you have time to click on the link? I tried recently and the Outlook flow worked as expected for me. I will give another shot in the nearest day and let you know.
Oh wait I just noticed the redirect scheme with https
, it may be the issue. The spawn server is really basic and may not support https in fact.
I also tried to bypass this by reusing the OAuth tokens from pizauth, with these config lines (but I think I may have misunderstood some of the config keys):
backend.auth.access-token.cmd = "pizauth show accountXXXX" backend.auth.refresh-token.cmd = "pizauth refresh accountXXXX"
Those are shell commands to retrieve the access token or the refresh token. So pizauth show accountXXXX
should definitely work (and should not require any himalaya account configure
).
Hi, I'm exploring the project to replicate my current email setup which use mu, mbsync, msmtp, and pizauth (OAuth token fetcher/daemon). I compiled himalaya from git with OAuth2 and keyring features enabled (the repository's head at the time of compilation was commit
92814d6
).The issue is that I can read mail from account using standard IMAP, but OAuth authentication fails for my Outlook work accounts. Since I am authenticating as Thunderbird (authorized with HTTPS redirects on localhost), attempting to fetch mail gives the following error:
Config snippet:
I also tried to bypass this by reusing the OAuth tokens from pizauth, with these config lines (but I think I may have misunderstood some of the config keys):
Some logs: