<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Haraka on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/haraka/</link>
    <description>Recent content in Haraka on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 10 May 2026 08:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/haraka/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Mail Routing and Transport Management: Postfix vs Exim vs Haraka</title>
      <link>https://www.pistack.xyz/posts/2026-05-10-self-hosted-mail-routing-transport-postfix-exim-haraka-guide/</link>
      <pubDate>Sun, 10 May 2026 08:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-10-self-hosted-mail-routing-transport-postfix-exim-haraka-guide/</guid>
      <description>&lt;p&gt;Mail routing is the backbone of any email infrastructure. When your organization hosts multiple domains, manages subdomain-based services, or needs to route mail between internal and external systems, a well-configured mail transport layer is essential. The three most widely used self-hosted solutions for mail routing are &lt;strong&gt;Postfix&lt;/strong&gt;, &lt;strong&gt;Exim&lt;/strong&gt;, and &lt;strong&gt;Haraka&lt;/strong&gt; — each with fundamentally different architectures and routing philosophies.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
