Your message dated Tue, 07 Aug 2018 09:05:14 +0000
with message-id <[email protected]>
and subject line Bug#905551: fixed in mutt 1.10.1-2
has caused the Debian Bug report #905551,
regarding mutt: add OAUTHBEARER auth support
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
905551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905551
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mutt
Version: 1.10.1-1
Severity: wishlist
Tags: upstream patch fixed-upstream
Hi,
As described in
http://lists.mutt.org/pipermail/mutt-dev/Week-of-Mon-20180611/000121.html,
Gmail supports RFC 7628 for oauth as a way of avoiding password based
auth. Applying three upstream patches gets mutt to support this
reasonably well:
1. 798f749eeeb98ed04028521a2eb3e505c1a83574 (Initial support for
OAUTHBEARER for IMAP, 2018-06-11)
2. fcd333986c0d15dec67870b7b74fef0e00e8c28b (Support for using
OAUTHBEARER for smtp, 2018-06-12)
3. 98cc42365ac97b0dfeafadf5561043e06744fcf6 (Improve OAUTHBEARER
support, 2018-06-26)
I'm running with those now, with the following configuration:
set from=<me>@gmail.com
set folder=imaps://<me>@[email protected]/
set smtp_url=smtps://<me>@[email protected]:465/
set spoolfile==INBOX
set imap_authenticators="oauthbearer"
set imap_user="<me>@gmail.com"
set imap_oauth_refresh_command="$HOME/bin/oauth2.py --quiet
--user=<me>@gmail.com --client_id=<client id> --client_secret=<client secret>
--refresh_token=<refresh token>"
set smtp_authenticators="oauthbearer"
set smtp_oauth_refresh_command="$HOME/bin/oauth2.py --quiet
--user=<me>@gmail.com --client_id=<client id> --client_secret=<client secret>
--refresh_token=<refresh token>"
It works like a charm. oauth2.py is [1]. <me> is $USER. <client id>,
<client secret>, and <refresh token> were generated following the
instructions at [2].
All three patches are in mutt "master", but I don't know how long it
will be until the next upstream release. What do you think of
applying the patches in the meantime? I'll send a debdiff in a
separate message.
Thanks,
Jonathan
[1] python/oauth2.py in https://github.com/google/gmail-oauth2-tools
[2]
https://github.com/google/gmail-oauth2-tools/wiki/OAuth2DotPyRunThrough#creating-and-authorizing-an-oauth-token
--- End Message ---
--- Begin Message ---
Source: mutt
Source-Version: 1.10.1-2
We believe that the bug you reported is fixed in the latest version of
mutt, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Radici <[email protected]> (supplier of updated mutt package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 07 Aug 2018 09:31:52 +0100
Source: mutt
Binary: mutt
Architecture: source
Version: 1.10.1-2
Distribution: unstable
Urgency: low
Maintainer: Mutt maintainers <[email protected]>
Changed-By: Antonio Radici <[email protected]>
Description:
mutt - text-based mailreader supporting MIME, GPG, PGP and threading
Closes: 905551
Changes:
mutt (1.10.1-2) unstable; urgency=low
.
[ Jonathan Nieder ]
* debian/patches:
+ added upstream patches for OAUTHBEARER support by Brandon Long
(Closes: #905551).
+ upstream/905551-oauthbearer-imap.patch
+ upstream/905551-oauthbearer-smtp.patch
+ upstream/905551-oauthbearer-refresh.patch
.
[ Antonio Radici ]
* New release to include the patch above.
Checksums-Sha1:
431ab042a81390788506704d0e675ad0277da13d 2351 mutt_1.10.1-2.dsc
0d6f35364c735529ca1ca99fdc3e5f3d4dc91461 62104 mutt_1.10.1-2.debian.tar.xz
d11efaea8641aae06567459fe8b04edfcb6aa5c5 8088 mutt_1.10.1-2_amd64.buildinfo
Checksums-Sha256:
4db888d3b2ed98949bed933b51a72873caf20e1f0b86c265a13769fc1ade7131 2351
mutt_1.10.1-2.dsc
751d3f6473ff4b8c55971a7d1497630ce2d447eb120647935310d52d275c6972 62104
mutt_1.10.1-2.debian.tar.xz
1ce53db81dbaeac501d0b16b3c599e60d4f51076d36ba9947c9df6f5fb288e61 8088
mutt_1.10.1-2_amd64.buildinfo
Files:
8bf7b6c61bc68fb81a6636cbdad9b709 2351 mail optional mutt_1.10.1-2.dsc
97e18b8fb693b7a534a47de1bb2a4994 62104 mail optional
mutt_1.10.1-2.debian.tar.xz
fe849e35fbd24eb86e77ec9bc48ca32f 8088 mail optional
mutt_1.10.1-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJHBAEBCAAxFiEEQObYrBkA1SRrfOa1NcjIiHLLHu0FAltpWsUTHGFudG9uaW9A
ZGViaWFuLm9yZwAKCRA1yMiIcsse7ZXzD/0RSaLF59wJknnQ/P/MoqspGavIVhqo
pTQbNvgvh3kCdaWcBFgIskEUDyHd/t/MVlvOPafA6d1JwRIDMgPdSZoggvF13c3W
t7tj8+aaP5fheS2b/JgLbYbPOh8/wayDVKN6WiNkLVVcsizwHoaZ7ztn74R5UB+b
5fZf3Ks+FiYQdwQUhGjzPyFJZEvxN3BV++hbVb1PnE3jQF01Xxwe1r5CuplHV7Op
y5KeSJv1UVA9D4vjkInCzQHn91hswfouaTBVGxt/XOq+Kiilvij+6ffKLNZoS+X7
2P+/ArplhAGa9qR0cNdX+f8udI4lgjOGKrvHfYvAfZksS9M4SHeJ40N+DtXcXFrp
g4hDSW37Ri801EUxBGWL9A13WfJAXx1SHoco86xGvIvf/D3riKEtciIj9ACts8qD
NbpiF7OnQb6Jz7JpH4JG2GbCatzdI6/G3Ef9xjYtcFSuiVfxTDhBWf/NAfIoJtDF
731v+HMGDtkSR/zo+Bkv2feOtjdNXmXU6V+NZstHZedXhgCiGPT+BDU9+J1slUKr
im8xDo1NKgc2r1SYz8sUL94kSGUBqj+457dxjmp9kkpCmvd4/oDakmbvcuxjrKAv
nsNMsO9If27nkmNdEoCGE4QJvsZAXJHQc9i70IfkHxY06vZMiDD8FzjUTpaZQGgV
K9IMsBD0ZkpWzw==
=o95P
-----END PGP SIGNATURE-----
--- End Message ---
