Dear Alpiners,
it is my pleasure to announce the release of version 2.24 of Alpine.
New features include the addition of XOAUTH2 support for Yahoo!, automatic renew of the access token before it expires, and improvements to the privacy of Alpine users.
Many thanks! I've just compiled an all-patched Alpine 2.24 because Yahoo
is discontinuing the "less secure" authentication method... tomorrow. In .pinerc I see at the bottom:
# Your client-id and client-secret information to authenticate using XOAUTH2 xoauth2-info=
Do I have anything to do now to have Alpine use XOAUTH2 to connect to
the Yahoo servers (IMAP, and SMTP if applicable)?
Dear Lucas,
I dcumented how to follow this process here
http://alpine.x10host.com/alpine/alpine-info/misc/xoauth2.html#SettingUpYahoo
in essence what you need is
a) a version of Alpine compiled with password file support
b) a password file
c) edit your piner, and add "/auth=xoauth2" to the definition of the yahoo
servers
d) Attempt to open your yahoo account and follow the authorization procedure.
Let me know if you have any questions. I will be happy to help you.
On Mon, 19 Oct 2020, Lucas Levrel wrote:
Many thanks! I've just compiled an all-patched Alpine 2.24 because Yahoo
is discontinuing the "less secure" authentication method... tomorrow. In >>.pinerc I see at the bottom:
# Your client-id and client-secret information to authenticate using XOAUTH2 >>xoauth2-info=
Do I have anything to do now to have Alpine use XOAUTH2 to connect to
the Yahoo servers (IMAP, and SMTP if applicable)?
Dear Lucas,
I dcumented how to follow this process here
http://alpine.x10host.com/alpine/alpine-info/misc/xoauth2.html#SettingUpYahoo
in essence what you need is
a) a version of Alpine compiled with password file support
b) a password file
c) edit your piner, and add "/auth=xoauth2" to the definition of the yhoo
servers
d) Attempt to open your yhoo account and follow the authorization
procedure.
Let me know if you have any questions. I will be happy to help you.
This isn't an alpine issue, but checking the Received headers for the interaction between the Yahoo Mail server and my local Mail server
(using TLSv1.2 with cipher (128/128 bits))
(No client certificate requested)
it's not clear to me whether Yahoo didn't request the certificate on my
end or my server didn't request Yahoo's certificate. Is a certificate required to be requested at this point?
On Wed, 18 Nov 2020, Adam H. Kerman wrote:
This isn't an alpine issue, but checking the Received headers for the
interaction between the Yahoo Mail server and my local Mail server
(using TLSv1.2 with cipher (128/128 bits))
(No client certificate requested)
it's not clear to me whether Yahoo didn't request the certificate on my
end or my server didn't request Yahoo's certificate. Is a certificate
required to be requested at this point?
My understanding is that this is an optional part of the ertification >process. A server can request a client to send a certificate, and is free
to do whatever it wants with the result of the validation of that
certificate (as in if the certificate is not sent or not valid, it can
either close of connection or continue it, just like clients do with
server certificates.)
I have never dealt with server that require certificates, so I do not have >use case for this.
Dear Alpiners,
it is my pleasure to announce the release of version 2.24 of Alpine.
The full list of new features and bug fixes can be read from the Release Notes, which can be reached from the Main Menu, by pressing the "R" key.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 295 |
Nodes: | 16 (2 / 14) |
Uptime: | 02:02:42 |
Calls: | 6,642 |
Calls today: | 2 |
Files: | 12,190 |
Messages: | 5,325,482 |