feat(email-service): Block users #1114
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Don't merge until we get gmail approval for elevated oauth scope in prod
Summary
Adds endpoints for blocking and unblocking email senders, as well as listing all currently blocked users.
New Endpoints
POST/email/contacts/blockDELETE/email/contacts/block/:email_addressGET/email/contacts/blockedHow It Works
Gmail does not allow external API callers to mark messages as
SPAM, so the best we can do is move messages from blocked users directly to trash. This is the same approach Superhuman uses when you block a user.Blocking is implemented by creating a Gmail filter for the sender's email address, which automatically moves their incoming messages to the trash.
This feature requires a new OAuth scope (
gmail.settings.basic) to manage Gmail filters. This means:403 Forbiddenif the user lacks the required Gmail permissions403is received, the UI should prompt the user to re-authenticate to grant the elevated permission