<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog on CentralBox — private, hosted email on your own domain</title>
    <link>https://centralbox.co/blog/</link>
    <description>Recent content in Blog on CentralBox — private, hosted email on your own domain</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 11 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://centralbox.co/blog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reputation isolation, by design</title>
      <link>https://centralbox.co/blog/reputation-isolation-by-design/</link>
      <pubDate>Sat, 11 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://centralbox.co/blog/reputation-isolation-by-design/</guid>
      <description>CentralBox owns one SES account for every tenant. Here&amp;rsquo;s how we keep one customer&amp;rsquo;s bounces from sinking another&amp;rsquo;s sender reputation.</description>
    </item>
    <item>
      <title>The inbound pipeline: SES → S3 → SNS → your inbox</title>
      <link>https://centralbox.co/blog/the-inbound-pipeline/</link>
      <pubDate>Sat, 11 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://centralbox.co/blog/the-inbound-pipeline/</guid>
      <description>A teardown of how mail sent to your verified domain actually lands in the CentralBox dashboard — and why idempotency has to be a first-class concern.</description>
    </item>
  </channel>
</rss>
