Proxmox Mail Gateway 9.1 Is a Boring Release in the Best Possible Way

# Proxmox Mail Gateway 9.1 Is a Boring Release in the Best Possible Way Proxmox Mail Gateway 9.1 didn’t spark a sprawling argument, which almost feels strange for infrastructure software. The post was just the release link, the score climbed, and the lone visible comment said, “Excellent work as always.” That tiny reaction says a lot. Mail security tools usually only become loud when something breaks, spam floods a domain, quarantine becomes a daily nuisance, or backups fail exactly when someone needs them. So a quiet, positive response to a mail gateway release lands differently. It sounds less like hype and more like relief. The kind of relief admins rarely admit they want. ## Email Security Is Where Fun Goes to Be Filtered Nobody gets into homelabbing because they dreamed of mail gateways. Email security is the unglamorous hallway behind the server room: spam scoring, quarantine links, ClamAV updates, Postfix plumbing, backup targets, user complaints, and that one executive who swears the missing message is business critical. Proxmox Mail Gateway sits right in that unpleasant gap between the firewall and the real mail server, filtering inbound and outbound traffic before it reaches the inbox. It is not sexy software. That’s exactly why it matters. The 9.1 release keeps that practical focus. Proxmox says the update brings refreshed core components, quarantine usability upgrades, and encryption options for backups. It’s built on Debian 13.5 “Trixie,” uses Linux kernel 7.0 as the stable default, and includes updated pieces like SpamAssassin 4.0.2, ClamAV 1.4.4, PostgreSQL 17, and ZFS 2.4. That list won’t make anyone throw a parade, but it’s the stuff a gateway lives on. Fresh filtering engines, current databases, modern storage, and a base OS that isn’t drifting into museum territory. [Proxmox](https://proxmox.com/en/about/company-details/press-releases/proxmox-mail-gateway-9-1) ## The Quarantine Changes Are Small Until You Need Them The best part of this release might be the quarantine improvements, because that’s where admin pain becomes user pain. Shared mailboxes can now mark quarantined emails as seen, so multiple people don’t waste time auditing the same message. That sounds tiny, but anyone who has managed team mailboxes knows how quickly “did you already check this?” becomes its own support process. The new inline seen status and toggle button are exactly the kind of low-drama feature that saves clicks without demanding a training session. Granular spam scoring is another practical win. Showing positive and negative score components at the same time helps explain why a message got caught instead of turning quarantine into a black box. Users may not care about the math, but admins do. A false positive is easier to discuss when the tool gives clues instead of shrugging. The same goes for copyable private quarantine links from the admin dashboard. It’s not flashy. It just removes one more awkward workaround from a workflow that already has enough of them. [Proxmox](https://proxmox.com/en/about/company-details/press-releases/proxmox-mail-gateway-9-1) ## The Image Loading Change Feels Quietly Smart One of the sharper features is on-demand image loading in quarantined emails. External images can be configured so they don’t automatically load when someone inspects a message. Instead, the user can click a “Load Images” button when they actually want to see them. That’s a small UI choice with a big security mood behind it. Quarantine is supposed to be a safer place to inspect sketchy mail, not a side door for trackers, remote content, or web-based surprises. This is the kind of feature that shows Proxmox understands the boring reality of mail administration. Users want to see whether a suspicious message is real. Admins want them to do that without lighting up a tracking pixel or pulling remote content from a hostile sender. Blocking images by default is not new as a security idea, but putting the control directly into the quarantine flow is the important part. The safest option becomes the easy option. That’s how security should feel. Not heroic, just harder to mess up. [Proxmox](https://proxmox.com/en/about/company-details/press-releases/proxmox-mail-gateway-9-1) ## Encrypted Backups Are the Adult Feature The backup change is where 9.1 gets serious. Proxmox added native encryption support for backups targeting a Proxmox Backup Server instance. The goal is client-side encryption before transmission, with data staying encrypted at rest on the backup target. That matters because a mail gateway doesn’t just hold disposable config. It can contain sensitive email policy, user-created rule data, historic and private statistics, and all the tiny details that describe how an organization defends its inboxes. This is one of those features that sounds obvious only after it exists. Of course mail gateway backups should be encrypted. Of course the backup server shouldn’t become the softer copy of the same sensitive system. But plenty of infrastructure grows by layers, and older workflows often survive longer than they should because they “work.” Native encryption support tightens that story. It makes the safe path feel like a first-class path, not a custom ritual taped together after the audit finds it. [Proxmox](https://proxmox.com/en/about/company-details/press-releases/proxmox-mail-gateway-9-1) ## The Quiet Comment Was the Whole Vibe With only one visible comment saying the work was excellent as always, there wasn’t much drama to mine. But that quietness fits the product. Proxmox Mail Gateway is not the shiny part of the Proxmox ecosystem. Proxmox VE gets the cluster screenshots. Proxmox Backup Server gets the disaster-recovery love. Datacenter Manager gets the new-control-plane attention. Mail Gateway is the guard dog by the inbox, and most people only look at it when it barks. That’s why the muted praise feels sincere. People who rely on mail security don’t necessarily want reinvention every release. They want the project to keep moving, update its base, smooth the daily workflows, harden backup handling, and not suddenly become weird. 9.1 seems aimed right at that expectation. It’s less “look at the future of email” and more “your quarantine is less annoying, your stack is fresher, and your backups can be safer.” Honestly, that’s probably exactly the pitch this product needs. ## Stability Is the Feature Nobody Screenshots Availability matters here too. Proxmox says Mail Gateway 9.1 is open-source and available now, with a complete ISO, installation on bare metal, installation on top of Debian, or deployment as a lightweight LXC on Proxmox VE. There’s also a tested upgrade path from PMG 8.2 or 9.0 through APT. Those details are boring until you’re the person planning the maintenance window. Then they become the whole story. A mail gateway can’t be treated like a toy VM. If it’s down, people notice fast. [Proxmox](https://proxmox.com/en/about/company-details/press-releases/proxmox-mail-gateway-9-1) So yes, Proxmox Mail Gateway 9.1 is not the kind of release that sends the community into a meme storm. Good. Mail security should not need fireworks to prove it’s alive. The strongest version of this product is one that quietly reduces friction and quietly improves safety. Better quarantine workflows. Safer image handling. Encrypted backup targets. Updated core components. A clean upgrade path. That’s not boring because nothing happened. It’s boring because the right things happened without drama. And for email infrastructure, drama is usually just another word for incident.