Re: Gmail/OAuth2

--===============5111004822595134633==
Content-Type: MULTIPART/SIGNED; protocol="application/pgp-signature"; micalg=pgp-sha1; BOUNDARY="8323329-1760243555-1746106503=:1212485"

--8323329-1760243555-1746106503=:1212485
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE

On Thu, 1 May 2025 00:34:17 -0600 Trevor <[email protected]> wrote:

T> Hi! I'm still using Mahogany after all these years (since about 2004).

 Hi,

 Glad to hear that there are still some users of Mahogany left!

T> It's been a few years since I checked the website and mailing lists and
T> it's great to see there's been some recent activity.

 I have to admit that I didn't do any serious work on Mahogany since years,
if not decades, but I do fix things that bother me personally from time to
time, as I still use it for handling all my email.

T> I've been using it for Gmail, via both POP3 and IMAP for various accounts.
T> However, Gmail has finally dropped support for legacy applications that use
T> only Username/Password credentials,

 It doesn't look like they already did:

$ openssl s_client -crlf -connect imap.gmail.com:993
[...]
* OK Gimap ready for requests from xxx.yyy.zzz.www g9mb50557697wmk
c01 capability
* CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER
c01 OK Thats all she wrote! g9mb50557697wmk
c02 logout
* BYE Logout Requested g9mb50557697wmk
c02 OK Quoth the raven, nevermore... g9mb50557697wmk

Note the presence of AUTH=PLAIN, so at least right now it should still be
possible to use Mahogany with GMail.

T> and it looks like I have to move to one that supports Oath2. As I also
T> plan to move from Windows to Linux, Mahogany still fits the bill. Any
T> plans on adding Oath2 to Mahogany? (or is it already there somewhere?)

 No, unfortunately not. Mahogany uses c-client library for dealing with all
this stuff, which means that implementing this would need to be done at
that level, which is more difficult for me than just modifying Mahogany
itself. But OTOH it's not the only application using this library and it
looks like Alpine (the successor to Pine) has already implemented it, see
https://repo.or.cz/alpine.git/blob/HEAD:/imap/src/c-client/oauth2_aux.c and
so perhaps we could just use their version.

 IOW this is not completely hopeless, but definitely requires some work. I
might have a look at this, but no promises. For now I've created https://github.com/vadz/mahogany/issues/1 which you can monitor if you'd like to know when/if anything happens there.

 Best regards,
VZ

--8323329-1760243555-1746106503=:1212485
Content-Type: APPLICATION/PGP-SIGNATURE

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQQx+vLQdOwioQqkxtoG6kHeT2wehgUCaBN4hwAKCRAG6kHeT2we
hkWbAKCkG/WDdBm5PxEY9+Z8AxnT6ePIUACgp9UpXNncQ6WnLpzvx3H4aIlHRFM=
=TcUM
-----END PGP SIGNATURE-----

--8323329-1760243555-1746106503=:1212485--


--===============5111004822595134633==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============5111004822595134633==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mahogany-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mahogany-users

--===============5111004822595134633==--