<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>The Outbox</title>
    <link>https://mailfully.com/blog</link>
    <description>Notes from the Mailfully team on deliverability, transactional email APIs, and the unglamorous plumbing that keeps mail out of the spam folder.</description>
    <language>en-us</language>
    <atom:link href="https://mailfully.com/blog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Getting Outbound Email to Work on DigitalOcean</title>
      <link>https://mailfully.com/blog/digitalocean-blocks-smtp-ports-ses-2587</link>
      <guid isPermaLink="true">https://mailfully.com/blog/digitalocean-blocks-smtp-ports-ses-2587</guid>
      <pubDate>Thu, 17 Sep 2026 20:24:05 GMT</pubDate>
      <description>Our Ghost install on a DigitalOcean droplet couldn&apos;t send its own invites, and weeks with support went nowhere. Amazon SES also answers on port 2587, and one number in the config fixed it.</description>
    </item>
    <item>
      <title>Send your transactional mail from a subdomain</title>
      <link>https://mailfully.com/blog/send-transactional-mail-from-a-subdomain</link>
      <guid isPermaLink="true">https://mailfully.com/blog/send-transactional-mail-from-a-subdomain</guid>
      <pubDate>Mon, 14 Sep 2026 15:03:47 GMT</pubDate>
      <description>SPF doesn&apos;t cascade to subdomains, and every name carries exactly one record. Put those together and sending from your root domain leaves you one DNS edit away from breaking every email your company sends.</description>
    </item>
  </channel>
</rss>
