Proxmox Mail Gateway 9.1 released!

t.lamprecht

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
6,855
5,353
315
South Tyrol/Italy
shop.proxmox.com
We are excited to announce the release of Proxmox Mail Gateway 9.1!

This release is based on Debian 13.5 "Trixie" and ships the Linux kernel 7.0 as the new stable default. It includes the latest versions of ZFS 2.4, PostgreSQL 17, SpamAssassin 4.0.2 (with updated rulesets), and ClamAV 1.4.4.

Some highlights of Proxmox Mail Gateway 9.1
  • Several usability improvements for the spam quarantine, available in both the desktop and the mobile-friendly interface:
    • Mark mails as seen for shared mailboxes.
    • See the summed positive and negative spam scores at a glance.
    • Optionally load external images in HTML mails only on demand.
    • Copy a quarantine login link for a recipient directly, in addition to the existing option of having such a link sent by email.
  • Improved Proxmox Backup Server integration:
    • Client-side backup encryption with key management and an optional master key for recovery.
    • Trigger a backup verification and see the encryption and verification state of each snapshot.
  • Show a configurable consent banner that must be acknowledged before login, for example for legal or usage notices.
  • Optionally log the envelope and decoded From, To, and Subject headers of each mail for auditing, disabled by default as the headers can contain personal data.
Beyond these additions, we've also implemented numerous performance enhancements and bug fixes to make your experience even smoother. For a full list of changes, check out our release notes.

Release notes
https://pmg.proxmox.com/wiki/Roadmap

Press release
https://www.proxmox.com/en/news/press-releases/

Download
https://www.proxmox.com/en/downloads

Alternate ISO download:
https://enterprise.proxmox.com/iso

Documentation
https://pmg.proxmox.com/pmg-docs

Community Forum
https://forum.proxmox.com

Bugtracker
https://bugzilla.proxmox.com

Source code
https://git.proxmox.com

Thank you for supporting the Proxmox Mail Gateway project! Your contributions and feedback, tests, bug reports and code contributions are always welcome!

FAQ
Q: Can I upgrade Proxmox Mail Gateway 9.0 to 9.1 with apt?
A: Yes, you can upgrade via the GUI updater or on the command line, for example via apt update && apt full-upgrade.

Q: Can I upgrade the latest Proxmox Mail Gateway 8 to 9 with apt?
A: Yes, please follow the upgrade instructions on https://pmg.proxmox.com/wiki/Upgrade_from_8_to_9

Q: How long will Proxmox Mail Gateway 8.2 receive bug fixes and security support?
A: Proxmox Mail Gateway 8.2 will receive security updates and critical bug fixes until August 2026. This support window provides an overlap of approximately one year after the release of Proxmox Mail Gateway 9.0, giving users ample time to plan their upgrade to the new major version. For more information on the support lifecycle of Proxmox Mail Gateway releases, please visit:
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#_frequently_asked_questions

Q: Can I install Proxmox Mail Gateway on top of Debian Trixie?
A: Yes, see https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmg_install_on_debian

Q: Can I install Proxmox Mail Gateway as a virtual machine on Proxmox Virtual Environment, VMware, or Hyper-V ?
A: Yes, just do the ISO install. If you install on Hyper-V as a generation 2 virtual machine, configure secure boot to use "Microsoft UEFI Certificate Authority".

Q: Can I install Proxmox Mail Gateway as LXC container on Proxmox Virtual Environment?
A: Yes. You can install it on top of a Debian container or just download the template via the integrated template downloader.

Q: Where can I get more information about feature updates?
A: Check the roadmap, forum, the mailing list, and/or subscribe to our newsletter.
 
  • Like
Reactions: Handwash3805, keeka, janssensm and 10 others
Hello,

great news!

Is the feature "Mark mails as seen for shared mailboxes" also available through the PMG API? I could not find any related endpoint or documentation in the API viewer.
 
I noticed that PMG 9.1 packages are already available through the Enterprise Repository and can be installed via regular updates.

Can you confirm that PMG 9.1 is considered stable and ready for production use?

I was a bit surprised to see it available in the Enterprise Repository already and wanted to double-check before upgrading.

Thanks!
 
torbho said:
Can you confirm that PMG 9.1 is considered stable and ready for production use?

I was a bit surprised to see it available in the Enterprise Repository already and wanted to double-check before upgrading.
Click to expand...
The released features and the complete system was tested thoroughly, was available in our public repositories, and has been live for our mail traffic for a while successfully. So to that extend I can confirm it's stable and in production use.

Of course all our testing cannot cover every single deployment, and, as with any regular update there is a chance for regressions - but until now we have received only one report about an issue related to changes released with 9.1 (https://forum.proxmox.com/threads/tracking-center-failed-after-update-to-latest.184208/) as far as I'm aware - which was fixed before the release.

You could consider setting up a cluster and upgrading one node at a time to verify everything works.

I hope that helps!
 
Are you planning for releasing an arm64 version, specifically as an ISO? It seems to me that it would not be very difficult to create that?
 
Great news!
But it would be good if the Block-button in the Spam Quarantine were separate again. We use this feature often, and the fact that it’s now hidden behind the Delete-button makes the workflow more cumbersome.
It would be great if this could be reversed.

Otherwise, a great release!
 
  • Like
Reactions: torbho
surinameclubcard said:
Are you planning for releasing an arm64 version, specifically as an ISO? It seems to me that it would not be very difficult to create that?
Click to expand...
not for 9.1 - but we might check that part out in the future - no promises when/if this will happen though.

I hope this helps!
 
Koch-IT said:
Great news!
But it would be good if the Block-button in the Spam Quarantine were separate again. We use this feature often, and the fact that it’s now hidden behind the Delete-button makes the workflow more cumbersome.
It would be great if this could be reversed.

Otherwise, a great release!
Click to expand...
FYI: there are also keyboard shortcuts for that, see the About docs tab. But we'll ch3ck if we can easily show that button dierectly if there's enough space.
 
  • Like
Reactions: Koch-IT
ran into a "fun" problem: I'm busy with a new deploy (using LXC template in PVE), and had /var/spool/pmg/ on a CEPHfs
the upgrade to 9.1 failed with pmg-api (9.1.0)'s package doing a chgrp -R /var/spool/pmg/, and then errors on /var/spool/pmg/.lost+found

Code: 
chgrp: cannot read directory '/var/spool/pmg/.lost+found': Permission denied
dpkg: error processing package pmg-api (--configure):
 
hvisage said:
ran into a "fun" problem: I'm busy with a new deploy (using LXC template in PVE), and had /var/spool/pmg/ on a CEPHfs
the upgrade to 9.1 failed with pmg-api (9.1.0)'s package doing a chgrp -R /var/spool/pmg/, and then errors on /var/spool/pmg/.lost+found
Click to expand...
Thanks for the report - seems the case of having /var/spool/pmg on a dedicated mount-point/filesystem in a container was missed while testing -
I sent a patch for discussion to the pmg-devel mailing-list. once this or an improved version has been merged the issue should be gone.

Out of curiosity - what was the specific idea behind putting the spooldir on a mountpoint of its own? (and how does the container config and storage config look like)?
 
  • Like
Reactions: hvisage and Johannes S
Stoiko Ivanov said:
Out of curiosity - what was the specific idea behind putting the spooldir on a mountpoint of its own? (and how does the container config and storage config look like)?
Click to expand...
Standard SysAdmin best practises from my perspective:
- tiny replaceable OS/root partitions
- Data storage to be separate from root/os storage
-- then moving it between faster(nvme zfs) vs redundant (read ceph) vs cheaper (HDD zfs) depending on the needs/requirements etc.
-- Also different settings like noatime vs atime (read like PBS storage requirements ;) )
 
Last edited:
  • Like
Reactions: Johannes S and Stoiko Ivanov
You must log in or register to reply here.
Top Bottom
Back