Unable to send emails (Access token does not have sufficient scope)

[heywoodlh]

I am using the aerc e-mail client and when I try to send any email I get the following error: "Access token does not have sufficient scope".

The email always sends successfully but I have to re-authenticate with Hydroxide and restart it in order to reconnect successfully to Protonmail. Is there something I'm doing that's wrong/causing this?

Hydroxide imap logs show this:

2020/05/13 14:15:46 IMAP server listening on 127.0.0.1:1143
2020/05/13 14:16:05 User "[omitted]" logged in via IMAP
2020/05/13 14:16:05 Synchronizing mailbox INBOX...
2020/05/13 14:17:19 Synchronizing mailbox INBOX: done.
2020/05/13 14:17:19 Synchronizing mailbox Sent...
2020/05/13 14:17:20 Synchronizing mailbox Sent: done.
2020/05/13 14:17:38 request failed: POST https://mail.protonmail.com/api/auth/refresh: [10013] Invalid refresh token
2020/05/13 14:17:39 warning: failed to check SRP modulus signature: openpgp: unsupported feature: public key algorithm 22
2020/05/13 14:17:39 request failed: GET https://mail.protonmail.com/api/addresses: [403] Access token does not have sufficient scope

Hydroxide smtp logs show this:

2020/05/13 14:15:46 SMTP server listening on 127.0.0.1:1025
2020/05/13 14:17:39 [omitted] logged in
2020/05/13 14:17:39 creating draft message
2020/05/13 14:17:40 uploading message body
2020/05/13 14:17:42 sending message

I saw this related issue Token insufficient scope but it was closed and according to your commits it seemed like the issue was resolved, which is why I'm opening a new issue.

[heywoodlh]

So I run aerc in a Docker container and it seems to only be an issue on MacOS. On my Linux laptop I don't have this issue. So I'm going to chalk it up to something weird with Docker networking on MacOS vs Linux (since there are some notable differences).

Anyway, closing now as I don't believe this is a Hydroxide issue but rather a networking issue with my Docker container on MacOS. Especially since I can't replicate the issue on my Linux machine.

[heywoodlh]

After further testing, this issue continues to occur whenever I send an email using aerc whether or not it is in Docker. So I am reopening this issue and would love any further assistance to get it resolved.

[tidux]

Hydroxide+aerc works together as of Hydroxide commit 4c7fd88d57cde39b8f967b86756f0e93e7d42dd3 and as of aerc commit 1687e558d3fae4d5622677c031bb9365a8c3e261.