<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mta-Sts on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/mta-sts/</link>
    <description>Recent content in Mta-Sts on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/mta-sts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted MTA-STS Policy Servers: postfix-mta-sts-resolver vs postfix-tlspol vs sts-mate (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-14-self-hosted-mta-sts-policy-servers-resolver-tlspol-sts-mate-guide/</link>
      <pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-14-self-hosted-mta-sts-policy-servers-resolver-tlspol-sts-mate-guide/</guid>
      <description>&lt;p&gt;Email encryption in transit is critical for protecting sensitive communications, but traditional SMTP has a fundamental flaw: it silently falls back to plaintext when TLS negotiation fails. An active attacker can exploit this by stripping TLS capabilities during the SMTP handshake, intercepting all email content. MTA-STS (Mail Transfer Agent Strict Transport Security, RFC 8461) solves this by allowing domain owners to publish a policy that mandates TLS for inbound mail, preventing downgrade attacks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
