<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Maildriply blog</title>
    <link>https://maildriply.com/blog</link>
    <atom:link href="https://maildriply.com/blog/feed.xml" rel="self" type="application/rss+xml" />
    <description>Engineering notes from Maildriply — email infrastructure, Gmail quirks, and what we ship.</description>
    <language>en-us</language>
    <lastBuildDate>Tue, 12 May 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>How Gmail open tracking actually works (and where it lies)</title>
      <link>https://maildriply.com/blog/how-gmail-open-tracking-works</link>
      <guid isPermaLink="true">https://maildriply.com/blog/how-gmail-open-tracking-works</guid>
      <pubDate>Tue, 12 May 2026 00:00:00 GMT</pubDate>
      <description>A practical breakdown of email open tracking inside Gmail — the pixel, the image proxy, deduplication, and the bot heuristics that determine whether an open is real.</description>
    </item>
    <item>
      <title>Why we only request gmail.send (and why it costs us)</title>
      <link>https://maildriply.com/blog/why-gmail-send-only-scope</link>
      <guid isPermaLink="true">https://maildriply.com/blog/why-gmail-send-only-scope</guid>
      <pubDate>Fri, 08 May 2026 00:00:00 GMT</pubDate>
      <description>The smallest Gmail OAuth scope means we can&apos;t read your inbox, which means a few features are harder to build. We think the tradeoff is worth it. Here&apos;s the math.</description>
    </item>
    <item>
      <title>Tracking pixels vs link tracking — pick the right signal</title>
      <link>https://maildriply.com/blog/tracking-pixels-vs-link-tracking</link>
      <guid isPermaLink="true">https://maildriply.com/blog/tracking-pixels-vs-link-tracking</guid>
      <pubDate>Sun, 03 May 2026 00:00:00 GMT</pubDate>
      <description>Open tracking is the most popular metric in email and one of the noisiest. Click tracking is harder to get right but tells you more. Here&apos;s how we use both.</description>
    </item>
  </channel>
</rss>