On Fri, Aug 21, 2020 at 03:25:12PM -0700, Kevin J. McCarthy wrote:
>
> Sorry for the delay. Applied.
For some of these contrib scripts that are in languages like shell /
Python / Perl / etc., would it be worth trying to setup some basic
linting in CI?
I'm not super familiar with gitlab CI,
On Sat, Aug 08, 2020 at 05:02:00PM -0500, Alexander Perlis wrote:
Attached is a newer version of the mutt_oauth2.py script that incorporates the
following changes:
- Uses /usr/bin/env at top
- Many formatting changes to appease pylint
- Improvement to POP test error message output
Also
Attached is a newer version of the mutt_oauth2.py script that incorporates the
following changes:
- Uses /usr/bin/env at top
- Many formatting changes to appease pylint
- Improvement to POP test error message output
Also attached is a README that has instructions for both Microsoft and
With the push to disable "legacy" protocols completely in a lot of
environments, even with XOAUTH2 support and the external script for
oauth, it's not really possible to use Mutt.
There still hasn't been anything in terms of adding mapi support as
well, right?
> On Jul 2, 2020, at 9:06 PM, Kevin J. McCarthy wrote:
>
> With your permission, I'll add this to the contrib directory and add a link
> in the manual.
Certainly. Attached is a new version.
(1) Token file is now encrypted by a pipe specified near the top of the
script. Edit to suit.
(2)
On Thu, Jul 02, 2020 at 01:37:00PM -0500, Alexander Perlis wrote:
With the attached mutt_oauth2.py script and a corresponding app
registration I successfully connected mutt to:
- Gmail account
- Microsoft consumer account (e.g., outlook.com)
- Microsoft work/school account (Office365 under an
> On Jun 14, 2020, at 8:54 PM, Kevin J. McCarthy wrote:
>
> I made a commit to master adding this yesterday. I did some testing on
> Gmail, but haven't gotten around to testing Microsoft platforms yet. I could
> definitely use some help there.
With the attached mutt_oauth2.py script and a
On Fri, Jun 05, 2020 at 11:09:33AM -0700, Kevin J. McCarthy wrote:
See also the <69f8180c-40de-b7b5-880b-0f0e9f998...@scss.tcd.ie>
thread. My current plan is to wait a couple more months to see if MS
gets on board with OAUTHBEARER. If not, I'll add the authentication
mechanism for Mutt 1.15.
On 5 Jun 2020, at 23:55, Alexander Perlis wrote:
>> On Jun 5, 2020, at 2:50 PM, Steve Karmeinsky wrote:
>>
>> If anyone can send me something in plain English that I can send to my
>> contact at MS (he was my account manager when I was at Demon Internet and we
>> licensed IE - long story),
> On Jun 5, 2020, at 1:09 PM, Kevin J. McCarthy wrote:
>
> My current plan is to wait a couple more months to see if MS gets on board
> with OAUTHBEARER. If not, I'll add the authentication mechanism for Mutt
> 1.15. It will still require an external token script though.
The Gmail token
> On Jun 5, 2020, at 2:50 PM, Steve Karmeinsky wrote:
>
> If anyone can send me something in plain English that I can send to my
> contact at MS (he was my account manager when I was at Demon Internet and we
> licensed IE - long story), he’s quite senior now ...
Microsoft's IMAP server
If anyone can send me something in plain English that I can send to my contact
at MS (he was my account manager when I was at Demon Internet and we licensed
IE - long story), he’s quite senior now ...
Steve
--
Sent from my iPhone
> On 5 Jun 2020, at 19:09, Kevin J. McCarthy wrote:
>
> On
On Fri, Jun 05, 2020 at 10:19:58AM -0700, Will Yardley wrote:
On Wed, Apr 10, 2019 at 04:57:50PM -0500, Alexander Perlis wrote:
In case it helps inform a decision, here's the OAuth2 status of several
IMAP providers:
OAUTHBEARER: Google, Yahoo, ATT, Comcast, Sky
XOAUTH2 only: Microsoft,
On Jun 5, 2020, at 12:19 PM, Will Yardley wrote:
>
> On Wed, Apr 10, 2019 at 04:57:50PM -0500, Alexander Perlis wrote:
>
>> In case it helps inform a decision, here's the OAuth2 status of several
>> IMAP providers:
>>
>> OAUTHBEARER: Google, Yahoo, ATT, Comcast, Sky
>> XOAUTH2 only:
Will Yardley wrote in
<20200605171958.gb70...@aura.veggiechinese.net>:
|On Wed, Apr 10, 2019 at 04:57:50PM -0500, Alexander Perlis wrote:
|> In case it helps inform a decision, here's the OAuth2 status of several
|> IMAP providers:
|>
|> OAUTHBEARER: Google, Yahoo, ATT, Comcast, Sky
|>
On Wed, Apr 10, 2019 at 04:57:50PM -0500, Alexander Perlis wrote:
> In case it helps inform a decision, here's the OAuth2 status of several
> IMAP providers:
>
> OAUTHBEARER: Google, Yahoo, ATT, Comcast, Sky
> XOAUTH2 only: Microsoft, AOL, Yandex
> Neither: Apple, Cox, Zoho, Mail.com,
In case it helps inform a decision, here's the OAuth2 status of several
IMAP providers:
OAUTHBEARER: Google, Yahoo, ATT, Comcast, Sky
XOAUTH2 only: Microsoft, AOL, Yandex
Neither: Apple, Cox, Zoho, Mail.com, GMX, FastMail, 1&1
For each service, I searched for the IMAP server name, then
XOAUTH2 is just OAUTHBEARER but based on an earlier draft, so yes, it's
very similar. We had to ship it at Google because we we're deprecating
oauth1 and our XOAUTH with it, and the rfc was taking longer than we'd
hoped.
Given the large population of outlook.com users, I'd be for supporting it,
On Wed, Apr 03, 2019 at 06:47:19PM -0500, Alexander Perlis wrote:
Mutt supports OAUTHBEARER. Would patches adding XOAUTH2 be welcome?
Authentication schemes and OAUTH/XOAUTH2/etc are not really my area.
I'm Cc'ing the original contributor of the OAUTHBEARER patches.
Brandon, I would greatly
RFC 7628 standardized the SASL OAuth2 binding under the name
OAUTHBEARER, but currently some servers (e.g., imap-mail.outlook.com)
advertise only the nonstandard precursor XOAUTH2. (Seems XOAUTH2 might
have come out of Google and also was adopted by others including
Microsoft. Later RFC 7628 came
20 matches
Mail list logo
