wasm-demo/demo/ermis-f/imap-protocol/cur/1600094995.22595.mbox:2,S

25 lines
1.2 KiB
Plaintext

MBOX-Line: From nicolson at google.com Wed Mar 4 13:07:59 2015
To: imap-protocol@u.washington.edu
From: =?UTF-8?B?SmFtaWUgTmljb2xzb24gKOWAquW/l+aYjik=?= <nicolson@google.com>
Date: Fri Jun 8 12:34:53 2018
Subject: [Imap-protocol] XOAUTH for Gmail IMAP and SMTP to stop working soon
Message-ID: <CACU8CfRveb+qVUxOVKPfxi=gGwpsYgXo7nmbRspSgybab9Y5tQ@mail.gmail.com>
Sorry for the Gmail-specific announcement, we're trying to reach everyone
we can.
The OAuth 1.0 (XOAUTH) authentication mechanism to Gmail IMAP and SMTP has
been deprecated in favor of XOAUTH2 for almost three years now, and will
stop being supported after April 20, 2015. Unfortunately, we still have
some traffic that is authenticating with XOAUTH, and those apps are going
to break after April 20 unless they switch to XOAUTH2.
The documentation for XOAUTH2 is at
https://developers.google.com/gmail/xoauth2_protocol . You can convert
existing OAuth 1.0 tokens to OAuth 2.0 tokens without user intervention by
following the instructions at
https://developers.google.com/accounts/docs/OAuth_ref#migration .
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20150304/35d693a8/attachment.html>