<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>spf on </title>
    <link>http://bgall.uk/tags/spf/</link>
    <description>Recent content in spf on </description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <copyright>Ben Gallagher</copyright>
    <lastBuildDate>Sat, 23 Aug 2025 10:47:24 +0100</lastBuildDate><atom:link href="http://bgall.uk/tags/spf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SPF Flattener Tool</title>
      <link>http://bgall.uk/posts/spf/</link>
      <pubDate>Sat, 23 Aug 2025 10:47:24 +0100</pubDate>
      
      <guid>http://bgall.uk/posts/spf/</guid>
      <description>Introducing My SPF FlattenerLately I&amp;rsquo;ve been scratching a very specific itch: SPF records. These tiny TXT records live in your DNS and tell receiving mail servers who is authorised to send email on behalf of your domain. When they work, you never notice them. When they don&amp;rsquo;t, your mail gets quietly thrown into the spam abyss. It turns out there are two gotchas baked right into the SPF specification: you only get ten DNS lookups and each string is limited to 255 bytes.</description>
    </item>
    
  </channel>
</rss>
