Changes to the Messaging Gateway's Content Encryption feature

Products

• Messaging Gateway

Issue/Introduction

Beginning in September 2025, with the release of Messaging Gateway 10.9.2 and newer, the Content Encryption feature will no longer require a separate license to enable and configure. 

The configuration page at Content > Content Encryption will allow Messaging Gateway to be configured to use an arbitrary SMTP relay for messages to be delivered to a Content Encryption service. New licenses and renewals specifically for the Messaging Gateway Content Encryption feature will no longer be sold.

For customers who want to continue using Email Content Encryption provided by Broadcom, a new PGP Encryption license can be purchased to allow Messaging Gateway to integrate with Broadcom's cloud based Email Encryption infrastructure.

Resolution

Renewing the Content Encryption license

The previous Messaging Gateway Content Encryption SKU has been discontinued and the Content Encryption configuration page unlocked in SMG 10.9.2. Content Encryption will continue to operate unlicensed for some time to allow customers time to choose a Content Encryption provider. SMG Customers can choose to purchase a license for the new Email Cloud PGP Encryption product for use as the Content Encryption relay or to engage with a third party encryption provider for email encryption services.

To renew Content Encryption through Broadcom

1. Engage with Broadcom or your partner sales team to buy a license for Email Cloud PGP Encryption
2. Complete and return the provisioning form that is included with the Email Cloud PGP Encryption license, even if the Content Encryption had already been provisioned. Reprovisioning the service for Broadcom's Policy Based Encryption is required to update the content encryption relay
3. Upon returning the provisioning form, a Global Customer Assistance case will be created to provision the ESS Cloud resources and relay
4. When provisioning is complete, the administrative contact on the provisioning form will be notified via email of the SMTP host and port to use for the Content Encryption relay
5. Configure Messaging Gateway to used the provisioned relay via the Content > Content Encryption page