<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>BIG BOX Hosting — Field notes</title>
    <link>https://bigboxhosting.com/blog/</link>
    <atom:link href="https://bigboxhosting.com/blog/rss.xml" rel="self" type="application/rss+xml" />
    <description>Engineering perspective on email infrastructure, deliverability, and the regulatory landscape from the BIG BOX Hosting operations team.</description>
    <language>en-gb</language>
    <copyright>© 2026 BIG BOX Hosting d.o.o.</copyright>
    <lastBuildDate>Wed, 22 Apr 2026 00:00:00 GMT</lastBuildDate>
    <generator>Astro static build</generator>
    <ttl>1440</ttl>
    <item>
      <title>DKIM key rotation playbook for 2026</title>
      <link>https://bigboxhosting.com/blog/dkim-key-rotation-2026/</link>
      <guid isPermaLink="true">https://bigboxhosting.com/blog/dkim-key-rotation-2026/</guid>
      <pubDate>Wed, 22 Apr 2026 00:00:00 GMT</pubDate>
      <author>hello@bigboxhosting.com (Mikael Vainiomaa)</author>
      <description>The procedure looks simple — generate a new key pair, publish on a new selector, configure the MTA. Three steps. Here is what actually goes wrong, and the operational sequence that prevents it.</description>
      <category>dkim</category>
      <category>authentication</category>
      <category>operations</category>
    </item>
  
  </channel>
</rss>