Re: OT: help with directly using oauth2 tokens in keyring

Tim,

Thank you for this.

On Thu Jun04'26 04:41:48PM, Community Support for Fedora Users wrote:

> On Wed, 2026-06-03 at 09:26 -0500, M L via users wrote:
> > Anyway, my question is if it is at all possible to access these
> > evolution tokens in the keyring for use with
> > mutt/neomutt/sylpheed/claws-mail/getmail6/fetchmail/whatever and use
> > them. So, if something like this were possible, I would still run
> > evolution once in a while to get new tokens issued,  but use these
> > other receiving and sending email agents.
> 
> That *may* not be possible...  If their system works like others I've
> had to deal with, when any mail client tries to connect to their server
> it determines *what* client that is, and expects the right credentials
> for that client.
> 
> e.g. I had to help an elderly lady with accessing her mail with Telstra
> on her laptop and on her phone.  Each mail client needed its own unique
> credentials.  They could tell whether it was her phone or laptop, and
> which application it was.  And it would not allow duplicate passwords
> between any of them.
> 
> It was a right pain to get it working, not helped by their support
> staff being unaware of these requirements.  They could get one thing to
> work for her, then when they tried to get another thing to work, it'd
> kill access to the prior thing.  It took some experimentation on my
> behalf to determine the problem, and an annoying amount of time using
> their tedious web interface for setting up app passwords and verifying
> each thing.  The only thing it was slack about was one password for any
> web browser (probably the worst application, security-wise, to trust).
> 
> > Any other option I could try?
> 
> If fetchmail can access their server (it supports quite a variety of
> protocols), you could use it to drag in your mail.

The mainline fetchmail does not support oauth2 so I was thinking of using getmail6. (I believe that fetchmail 7 supports it since 2019 or so, but the main fetchmail developer appears to not be keen on it and I would not like to have the hassle of tracking these releases: Fedora ships with fetchmail mainline.)

> Other than that, I don't know if mutt allows you to fake data so it can
> pretend that it's one of their allowed mail clients.

Right, that is what I was wondering if it was at all possible. Perhaps I will ask on the mutt mailing list.

There is another possible option that I have come across. The first is  https://github.com/simonrob/email-oauth2-proxy which seems to run a local proxy server and is meant for clients that do not understand how to interact with oauth2 (like fetchmail mainline, I guess). 

But I can not figure out if it can take the tokens from the keyring, while I guess pretending to be evolution.

There is also https://github.com/pdobsan/oama which appears to store tokens in a keyring, but figure out insructions for mutt/neomutt (or getmail6) to take it from there.

Thanks for your thoughts!

M L 


-- 
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new