<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>DKIM on Nalar</title>
    <link>https://nalar.dev/tags/dkim/</link>
    <description>Recent content in DKIM on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/dkim/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SMTP Does Not Grant Sender Identity: From Headers, SPF, DKIM, and DMARC</title>
      <link>https://nalar.dev/smtp-sender-identity-from-spf-dkim-dmarc/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/smtp-sender-identity-from-spf-dkim-dmarc/</guid>
      <description>&lt;p&gt;SMTP answers a transport question: which server accepts this message and relays it toward its destination? It does not, by itself, prove that the address displayed in the message&amp;rsquo;s &lt;code&gt;From:&lt;/code&gt; header belongs to the system that opened the SMTP connection.&lt;/p&gt;&#xA;&lt;p&gt;That distinction explains a common surprise. A mail client can connect to an external SMTP service, authenticate successfully, and submit a syntactically valid message with &lt;code&gt;From: user@gmail.com&lt;/code&gt;. The SMTP login proves that the client may use that service. It does not give the service authority over &lt;code&gt;gmail.com&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
