<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Hermes SEG</title>
    <link>https://lists.hermesseg.io</link>
    <description>Mailing list archive</description>
    <item>
      <title>Hermes SEG is now a complete self-hosted email platform — and it runs on Docker</title>
      <link>https://lists.hermesseg.io/archive/1e7cb794-28e8-40f3-92ab-4311a40f9239</link>
      <description></description>
      <content:encoded><![CDATA[<!doctype html>
<html>
    <head>
        <title>Hermes SEG is now a complete self-hosted email platform — and it runs on Docker</title>
        <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
        <meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1">
        <base target="_blank">
        <style>
            body {
                background-color: #F0F1F3;
                font-family: 'Helvetica Neue', 'Segoe UI', Helvetica, sans-serif;
                font-size: 15px;
                line-height: 26px;
                margin: 0;
                color: #444;
            }

            pre {
                background: #f4f4f4f4;
                padding: 2px;
            }

            table {
                width: 100%;
                border: 1px solid #ddd;
            }
            table td {
                border-color: #ddd;
                padding: 5px;
            }

            .wrap {
                background-color: #fff;
                padding: 30px;
                max-width: 525px;
                margin: 0 auto;
                border-radius: 5px;
            }

            .button {
                background: #0055d4;
                border-radius: 3px;
                text-decoration: none !important;
                color: #fff !important;
                font-weight: bold;
                padding: 10px 30px;
                display: inline-block;
            }
            .button:hover {
                background: #111;
            }

            .footer {
                text-align: center;
                font-size: 12px;
                color: #888;
            }
                .footer a {
                    color: #888;
                    margin-right: 5px;
                }

            .gutter {
                padding: 30px;
            }

            img {
                max-width: 100%;
                height: auto;
            }

            a {
                color: #0055d4;
            }
                a:hover {
                    color: #111;
                }
            @media screen and (max-width: 600px) {
                .wrap {
                    max-width: auto;
                }
                .gutter {
                    padding: 10px;
                }
            }
        </style>
    </head>
<body style="background-color: #F0F1F3;font-family: 'Helvetica Neue', 'Segoe UI', Helvetica, sans-serif;font-size: 15px;line-height: 26px;margin: 0;color: #444;">
    <div class="gutter" style="padding: 30px;">&nbsp;</div>
    <div class="wrap" style="background-color: #fff;padding: 30px;max-width: 525px;margin: 0 auto;border-radius: 5px;">
        
<h2 style="margin:0 0 16px;font-size:22px;line-height:1.3;color:#1a1a1a;">Hermes SEG is now a complete self-hosted email platform — and it runs on Docker.</h2>

<p style="margin:0 0 16px;font-size:15px;line-height:1.6;color:#333;">Hermes Secure Email Gateway started as a security gateway you put in front of someone else's mail server. It has grown into something bigger: a <strong>complete self-hosted email platform</strong> — a full mail server, groupware (calendars, contacts, file sync, webmail), single sign-on, and the security layer that started it all, in one install. And as of <strong>v260612</strong> — our first public Docker release — you bring the whole stack up with a single <code style="background:#f4f1ec;padding:1px 5px;border-radius:4px;">docker compose up -d</code> instead of a bare-metal Ubuntu build. Run Hermes as your entire mail platform, or keep it in front of an existing one.</p>

<p style="margin:0 0 8px;font-size:16px;font-weight:700;color:#1a1a1a;">What Hermes is now</p>
<ul style="margin:0 0 20px;padding-left:20px;font-size:15px;line-height:1.6;color:#333;">
<li><strong>Still a secure email gateway</strong> — the original job hasn't gone anywhere. Run Hermes purely as a filtering gateway in front of Microsoft 365, Google Workspace, or any existing mail server, and nothing else changes.</li>
<li><strong>A full mail server</strong> — Dovecot 2.4 mailbox hosting over IMAPS / POP3S / submission / LMTP, per-domain and per-mailbox quotas, shared mailboxes and folders, and user-defined Sieve rules.</li>
<li><strong>Groupware built in</strong> — Nextcloud delivers webmail, calendars, contacts, and file sync, all behind one login.</li>
<li><strong>One Docker stack</strong> — 19 containers, a single compose file, no host-level mail services. Free and open source (AGPLv3).</li>
</ul>

<p style="margin:0 0 8px;font-size:16px;font-weight:700;color:#1a1a1a;">Security that's always free</p>
<p style="margin:0 0 8px;font-size:14px;line-height:1.6;color:#555;">The entire security stack ships in the free Community Edition — it's never behind the paywall.</p>
<ul style="margin:0 0 20px;padding-left:20px;font-size:15px;line-height:1.6;color:#333;">
<li><strong>Spam &amp; malware filtering</strong> — Postfix postscreen, RBLs, and an allow/block list up front; SpamAssassin and ClamAV behind it with <strong>ten signature feeds</strong> (SaneSecurity, URLhaus, MalwarePatrol and more) updated on a schedule. Per-user quarantine you can search, release, and train from.</li>
<li><strong>Encryption as table stakes</strong> — SMTP TLS in transit, S/MIME and PGP end-to-end, encrypted-PDF delivery for recipients without keys, and Dovecot mail-crypt encrypting every mailbox at rest. Internal CA managed from the console.</li>
<li><strong>Email authentication done right</strong> — SPF, DKIM (signed outbound and verified inbound), DMARC with report aggregation, and ARC to keep forwarded mail's auth chain intact — all managed from the UI, no shell rituals.</li>
<li><strong>Identity, MFA &amp; SSO</strong> — Authelia single sign-on across the console, user portal, webmail, and Nextcloud; TOTP / WebAuthn / Duo Push; app passwords for IMAP/SMTP/DAV clients; Have-I-Been-Pwned checks that block breached passwords at change time.</li>
</ul>

<p style="margin:0 0 8px;font-size:16px;font-weight:700;color:#1a1a1a;">Hermes Pro — the operational add-ons</p>
<p style="margin:0 0 8px;font-size:14px;line-height:1.6;color:#555;">Pro is an optional commercial layer, licensed per server, for production and managed-service deployments. Seven features on top of CE — your security stays free either way.</p>
<ul style="margin:0 0 20px;padding-left:20px;font-size:15px;line-height:1.6;color:#333;">
<li><strong>Link Guard</strong> — time-of-click link protection. Inbound links are rewritten and their reputation checked <em>at the moment of the click</em> (URLhaus, OpenPhish, optional Safe Browsing / VirusTotal), catching links weaponized after delivery — the defense you'd normally buy from Proofpoint or Mimecast, fully self-hosted.</li>
<li><strong>Let's Encrypt automation</strong> — hands-off ACME issuance and renewal for the admin console and per-domain mail TLS.</li>
<li><strong>LDAP RemoteAuth</strong> — per-domain pass-through authentication against Active Directory or other external LDAP.</li>
<li><strong>Intrusion Prevention &amp; Console firewall</strong> — web UIs to tune Fail2ban jails and lock the admin console to trusted networks, no SSH required.</li>
<li><strong>Disclaimers &amp; organizational signatures</strong> — centrally-managed, per-domain outbound footers and signatures applied at the milter level, so every message is covered regardless of client.</li>
</ul>

<div style="margin:0 0 24px;padding:14px 16px;background:#fdf6ea;border-left:3px solid #f0a000;border-radius:4px;font-size:14px;line-height:1.6;color:#444;"><strong>One honest heads-up:</strong> this is an early-adopter release. It's validated on our infrastructure, but if you run a production gateway, stand v260612 up <strong>in parallel</strong> and run your own acceptance tests before cutting over. It's <strong>fresh-install only</strong> for now — legacy migration tooling is still in progress.</div>

<table role="presentation" cellpadding="0" cellspacing="0" style="margin:0 0 24px;"><tr>
<td style="padding-right:10px;"><a href="https://github.com/deeztek/Hermes-Secure-Email-Gateway/releases/tag/v260612" style="display:inline-block;background:#f0a000;color:#ffffff;text-decoration:none;font-weight:600;font-size:14px;padding:11px 20px;border-radius:6px;">Read the full release notes →</a></td>
<td><a href="https://github.com/deeztek/Hermes-Secure-Email-Gateway#installation" style="display:inline-block;background:#ffffff;color:#c08000;text-decoration:none;font-weight:600;font-size:14px;padding:10px 19px;border:1px solid #f0a000;border-radius:6px;">Get started →</a></td>
</tr></table>

<p style="margin:0 0 16px;font-size:15px;line-height:1.6;color:#333;">Thanks for following along — early-adopter feedback shapes the next release directly.<br>— The Hermes SEG team</p>

<p style="margin:0;font-size:13px;line-height:1.5;color:#888;font-style:italic;">First time hearing from us at this address? We've moved our newsletter to a new system — same Hermes SEG updates, nothing else changes. Unsubscribe anytime below.</p>

    </div>
    
    <div class="footer" style="text-align: center;font-size: 12px;color: #888;">
        <p>
            <a href="https://lists.hermesseg.io/subscription/1e7cb794-28e8-40f3-92ab-4311a40f9239/" style="color: #888;">Unsubscribe</a>
            &nbsp;&nbsp;
            <a href="https://lists.hermesseg.io/campaign/1e7cb794-28e8-40f3-92ab-4311a40f9239/" style="color: #888;">View in browser</a>
        </p>
    </div>
    <div class="gutter" style="padding: 30px;">&nbsp;<img src="https://lists.hermesseg.io/campaign/1e7cb794-28e8-40f3-92ab-4311a40f9239/00000000-0000-0000-0000-000000000000/px.png" alt="" /></div>
</body>
</html>
]]></content:encoded>
      <pubDate>Tue, 23 Jun 2026 11:39:12 +0000</pubDate>
    </item>
  </channel>
</rss>