From cda59c7dff046f2c9ec1af680077b82568db45b7 Mon Sep 17 00:00:00 2001 From: Christopher Paris Date: Fri, 7 Mar 2025 23:45:11 -0500 Subject: [PATCH] Add oama file for mu4e --- .config/oama/config.yaml | 51 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+) create mode 100644 .config/oama/config.yaml diff --git a/.config/oama/config.yaml b/.config/oama/config.yaml new file mode 100644 index 0000000..f595a01 --- /dev/null +++ b/.config/oama/config.yaml @@ -0,0 +1,51 @@ +## oama version 0.16 + +## This is a YAML configuration file, indentation matters. +## Double ## indicates comments while single # default values. +## Not all defaults are shown, for full list run `oama printenv` +## and look at the `services:` section. + +## Possible options for keeping refresh and access tokens: +## GPG - in a gpg encrypted file $XDG_STATE_HOME/oama/.oauth +## (XDG_STATE_HOME defaults to ~/.local/state) +## GPG - in a gpg encrypted file ~/.local/state/oama/.oauth +## KEYRING - in the keyring of a password manager with Secret Service API +## +## Choose exactly one. + +encryption: + tag: KEYRING + +# encryption: +# tag: GPG +# contents: your-KEY-ID + +## Builtin service providers +## - google +## - microsoft +## Required fields: client_id, client_secret +## +services: + google: + client_id: 721790901363-ergskvjp6qcufl8hd1tujas6krj6ch64.apps.googleusercontent.com + client_secret: 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 + # auth_scope: https://mail.google.com/ + + # microsoft: + # client_id: application-CLIENT-ID + # client_secret: application-CLIENT_SECRET + # auth_scope: https://outlook.office.com/IMAP.AccessAsUser.All + # https://outlook.office.com/SMTP.Send + # offline_access + # tenant: common + + ## User configured providers + ## Required fields: client_id, client_secret, auth_endpoint, auth_scope, token_endpoint + ## + ## For example: + # yahoo: + # client_id: application-CLIENT-ID + # client_secret: application-CLIENT_SECRET + # auth_endpoint: EDIT-ME! + # auth_scope: EDIT-ME! + # token_endpoint: EDIT-ME!