| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This reverts commit 8b5859319347a0da80e9d7fd4dd1a7b5dec84e52.
Reason for revert: Google has fixed the upstream issue and this is not necessary anymore.
Change-Id: Ib1f7cfbc0e7e0997239514e9be75d2deab8c3c67
Reviewed-on: https://cl.tvl.fyi/c/depot/+/961
Tested-by: BuildkiteCI
Reviewed-by: glittershark <grfn@gws.fyi>
|
|
There is a temporary issue affecting the retrieval of discovery
documents in the Google Mail API:
https://issuetracker.google.com/issues/160441983
It's possible to work around this by hardcoding the document instead
of retrieving it over the network, as all other API calls still work
as they should.
This does exactly that by generating a patch to apply to lieer, from
the file checked in to the depot with this commit.
This workaround should be reverted once Google has fixed the issue
upstream.
Change-Id: I0063d0bc67753ffa5261c2aa059c7bfd09136ba0
Reviewed-on: https://cl.tvl.fyi/c/depot/+/945
Tested-by: BuildkiteCI
Reviewed-by: isomer <isomer@tvl.fyi>
|
|
|
|
It turns out I'm going to need multiple different OAuth clients for a
variety of reasons. This defaults to the client for tazj.in accounts,
but I use a different one in my work overlay.
|
|
Turns out that for some peculiar reason, the 'send' scope is not
enough to send email and the full 'mail.google.com' scope is required.
|
|
This makes it possible to reuse the lieer tokens for sending emails
from XOAUTH2-compatible SMTP clients.
|
|
This is now done in my work-specific configuration, which is
elsewhere.
|
|
|
|
|
