<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sieve on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/sieve/</link>
    <description>Recent content in Sieve on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 12 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/sieve/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Email Sieve Filtering: Pigeonhole vs Rspamd Sieve vs Cyrus Sieve</title>
      <link>https://www.pistack.xyz/posts/2026-05-12-self-hosted-email-sieve-filtering-pigeonhole-rspamd-cyrus-guide/</link>
      <pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-12-self-hosted-email-sieve-filtering-pigeonhole-rspamd-cyrus-guide/</guid>
      <description>&lt;p&gt;Email filtering is a critical component of any self-hosted mail infrastructure. While spam filters like Rspamd and SpamAssassin handle the initial wave of unwanted messages, the &lt;a href=&#34;https://en.wikipedia.org/wiki/Sieve_(mail_filtering_language)&#34;&gt;Sieve&lt;/a&gt; filtering language provides a standardized, server-side mechanism for organizing, tagging, redirecting, and manipulating email after delivery. Sieve scripts run on the IMAP/LDA server, enabling users to create sophisticated rules for sorting newsletters into folders, auto-forwarding critical messages, rejecting specific senders, and much more — all without relying on client-side filtering.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
