<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gmail Api - Tag - Dimas Maulana</title>
    <link>https://dimasmaulana.pages.dev/tags/gmail-api/</link>
    <description>Dimas Maulana Website</description>
    <generator>Hugo 0.165.0 &amp; FixIt v0.4.5</generator>
    <language>en</language>
    <lastBuildDate>Thu, 07 May 2026 00:10:23 +0000</lastBuildDate>
    <atom:link href="https://dimasmaulana.pages.dev/tags/gmail-api/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Use Least-Privilege Gmail Sending for WordPress Email</title>
      <link>https://dimasmaulana.pages.dev/posts/software/least-privilege-gmail-sending-wordpress/</link>
      <pubDate>Thu, 07 May 2026 00:10:23 +0000</pubDate>
      <guid>https://dimasmaulana.pages.dev/posts/software/least-privilege-gmail-sending-wordpress/</guid>
      <category domain="https://dimasmaulana.pages.dev/categories/software/">Software</category>
      <category domain="https://dimasmaulana.pages.dev/categories/troubleshooting/">Troubleshooting</category>
      <description>&lt;p&gt;Some WordPress mail integrations ask for broad Gmail access even though the site only needs to send messages. That is more access than a contact form, password reset, or transactional email workflow should need.&lt;/p&gt;&#xA;&lt;p&gt;The risk is not abstract. A broad Gmail permission can give an integration visibility into mail that has nothing to do with WordPress. If the site only needs to submit outgoing messages, there is no good operational reason to grant it the ability to read the mailbox as well.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
