Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
AUTOMATICALLY VERIFIEDOFFICIAL VENDOR SOURCECOLLECTED 25 SEP 2026

Proxmox · AUTOMATIC DISCOVERY

Proxmox Mail Gateway Lifecycle policy

Proxmox Mail Gateway is tracked by BlackTree as a server-side software product. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.

Evidence status

This record passed BlackTree's automatic primary-source checks with a confidence score of 82. It is returned for operational research without requiring routine manual approval. Confirm edition and deployment applicability before acting.

This discovery does not establish a product-specific support or retirement date. A missing date does not mean support continues.

Product overview

Proxmox Mail Gateway is tracked by BlackTree as a server-side software product. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.

Main capabilities

  • Networked or application service delivery
  • Administrative and operational interfaces
  • Versioned maintenance and security updates

Typical use

Used to provide application, infrastructure or operational services to other systems and users.

Deployment

Deployed on servers, virtual machines, containers or managed infrastructure.

This category-level context is generated from the registered product identity. Confirm exact product capabilities on the publisher's page .

Collected lifecycle data

ProductProxmox Mail Gateway
ReleaseLifecycle policy
Start or releaseNot extracted
Lifecycle boundaryContinuous or not dated in the source
Date precisionUnknown

Known exploited vulnerabilities

Catalogue updated 1 Oct 2026

These are product-family matches in the CISA Known Exploited Vulnerabilities catalogue. Confirm the affected product version in the vendor advisory.

No CISA known-exploited entries currently match this mapped product family.

This does not mean the product has no vulnerabilities.

Package vulnerability advisories

Checked 28 Sep 2026

OSV advisories are matched through the registered package URL. A package-family match does not prove that the installed release is affected. Check the affected and fixed versions before remediation.

No package advisories have been linked for this product identity.

This is not evidence that the product has no vulnerabilities.

Source evidence

PRIMARYManual

Proxmox Mail Gateway official lifecycle source

Provide the information needed for joining a Proxmox Mail Gateway cluster as a copy-pasteable base64 encoded string. The functionality is inspired by Proxmox VE, providing this UX improvement for a few years now. | Provide feedback on joining a cluster by showing the progress before reloading the view on success. Previously the user would be logged out during the process and had to log in again to verify that the join succeeded. | Expose the accept_broken_mime hardening setting in the mail proxy option configuration. | The mobile quarantine interface based on the Rust-based Yew framework got improved significantly with the feedback received since its release: The realm selector on the login page has no use for quarantine access and has been removed. Clicking on an action link for a particular quarantined mail now executes the corresponding function instead of only selecting the mail. An about page informing end-users about the functionality of the interface was added, as present on the desktop version of the interface ( issue 6852 ). After delivering or deleting an email in the mobile view, the list of emails is now refreshed automatically. | Add support for creating Proxmox Backup Server remotes with client-side encryption and provide comfortable key management ( issue 3326 ). Keys can be auto-generated, or existing keys can be uploaded. Users are prompted to download and store the key in a secure location to prevent accidentally losing access to their Proxmox Mail Gateway backups. | Fix an issue that caused users to be logged out on certain actions, like restoring a backup, or joining a cluster. Treating a non-existing authentication key file as an internal server error instead of the default authorization-required issue prevents users from being logged out after the action. | A consent banner can optionally be displayed before allowing logging in to the admin backend. This functionality was copied from Proxmox VE and Proxmox Backup Server and is a requirement in certain jurisdictions.

Publisher identity used by product-specific official-source collectors.

First collected 12 Sep 2026 · Last collected 25 Sep 2026 · Review state accepted

Open official vendor source