Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Gmail reference in regard to OAuth2 (and fix typos) in README.md #303

Merged
merged 1 commit into from
Sep 3, 2024
Merged

Remove Gmail reference in regard to OAuth2 (and fix typos) in README.md #303

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,11 +105,11 @@ reason for that is to respect user-choice of changing these values.

With the top-level option `oauth2=AUTHORIZER` you can specify,
that emails on the given domains support OAuth2 with the given authorizers.
Supported authorizers are `yandex` and `gmail`.
Supported authorizer is `yandex`.

In contrast to other authorization methods, you cannot use oauth2
In contrast to other authorization methods, you cannot use OAuth2
only because the server may support it.
New Oauth2 authorizers require adaptions in deltachat-core
New OAuth2 authorizers require adaptions in deltachat-core
and typically also bureaucratic effort.

### Use OAuth2 together with other options
Expand All @@ -124,7 +124,7 @@ so it is not needed to say sth. about OAuth2 before login.
All other options are applied as usual.


## limit RCPT TO header
## Limit RCPT TO header

With the `opt` option `max_smtp_rcpt_to: MAX`
you can set the maximum number of recipients
Expand Down
Loading