<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Amavis on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/amavis/</link>
    <description>Recent content in Amavis on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/amavis/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Email Quarantine Management: MailWatch vs MailZu vs amavisd-new Quarantine Release (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-06-01-self-hosted-email-quarantine-management-mailwatch-mailzu-amavisd-guide/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-01-self-hosted-email-quarantine-management-mailwatch-mailzu-amavisd-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Email quarantine is the unsung hero of self-hosted mail infrastructure. When your spam filter correctly identifies a malicious message, that message doesn&amp;rsquo;t disappear — it goes into quarantine, where it waits for administrative review. Without a proper quarantine management interface, your users are left wondering where their missing emails went, and administrators must manually sift through raw quarantine databases or log files to release false positives. &lt;strong&gt;MailWatch&lt;/strong&gt;, &lt;strong&gt;MailZu&lt;/strong&gt;, and &lt;strong&gt;amavisd-new&amp;rsquo;s built-in quarantine release&lt;/strong&gt; represent three approaches to solving this problem, from the full-featured MailWatch dashboard to the lightweight MailZu interface to amavisd&amp;rsquo;s native SQL quarantine tools.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
