Title: gmail api scope
Last modified: February 23, 2023

---

# gmail api scope

 *  [dbeacowp](https://wordpress.org/support/users/dbeacowp/)
 * (@dbeacowp)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/gmail-api-scope/)
 * Can you please consider changing the google API scope request to:
 * scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fgmail.send
 * Note: current it is: scope=https%3A%2F%2Fmail.google.com%2F
 * Post SMTP should only require the ability to send email and should not have the
   ability to read, delete or permanently delete email in the mailbox. This is analogous
   to SMTP which only allows sending of emails – not reading or deleting of emails.
 * This will change the oauth screen from “Read, compose, send, and permanently 
   delete all your email from Gmail” to “
   Send email on your behalf”

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [M Haseeb](https://wordpress.org/support/users/haseeb0001/)
 * (@haseeb0001)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/gmail-api-scope/#post-16498360)
 * Hi [@dbeacowp](https://wordpress.org/support/users/dbeacowp/)
 * I hope you are doing well.
 * Thanks for sharing your thoughts. The minimum scope we may require here is to
   compose since we need to create and send an email. We can switch to [https://www.googleapis.com/auth/gmail.compose](https://www.googleapis.com/auth/gmail.compose),
   Which grants permission to Create, read, update, and delete drafts. Send messages
   and drafts. We may commit to this change in the future if we find it stable to
   release these changes.
 * In the meantime, let us know if there is anything else we can help you with.
 * Thanks and regards,
 * Support Team – WPExperts
 *  Thread Starter [dbeacowp](https://wordpress.org/support/users/dbeacowp/)
 * (@dbeacowp)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/gmail-api-scope/#post-16500922)
 * I disagree with your response. You should not need h[ttps://www.googleapis.com/auth/gmail.compose](https://www.googleapis.com/auth/gmail.compose).
   Providing this level of access is still a security risk as Post SMTP would have
   the ability to read draft emails and delete draft emails that are unrelated to
   Post SMTP.
 * I have configured Post SMTP using [https://www.googleapis.com/auth/gmail.send](https://www.googleapis.com/auth/gmail.send)
   and it works perfectly.
 * When providing traditional SMTP configuration via an SMTP server Post SMTP would
   only have the ability to send – which is exactly the same access as the API scope
   I recommended. By providing a traditional SMTP server configuration, Post SMTP
   could not read the draft folder or delete it’s contents, this would require POP3
   or IMAP access.
 * I implore you to test and implement [https://www.googleapis.com/auth/gmail.send](https://www.googleapis.com/auth/gmail.send)
 *  [M Haseeb](https://wordpress.org/support/users/haseeb0001/)
 * (@haseeb0001)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/gmail-api-scope/#post-16502426)
 * Thanks for the update; I will follow up on this and update you once we update
   this commit.
 * Thanks

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘gmail api scope’ is closed to new replies.

 * ![](https://ps.w.org/post-smtp/assets/icon-128x128.gif?rev=3209655)
 * [Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App](https://wordpress.org/plugins/post-smtp/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/post-smtp/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/post-smtp/)
 * [Active Topics](https://wordpress.org/support/plugin/post-smtp/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/post-smtp/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/post-smtp/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [M Haseeb](https://wordpress.org/support/users/haseeb0001/)
 * Last activity: [3 years, 3 months ago](https://wordpress.org/support/topic/gmail-api-scope/#post-16502426)
 * Status: not resolved