DPG Service release 7.1.1483.0

Release date: November 6, 2025

In the following, we describe the changes that have been made to all versions of DPG Service that are still supported. Release notes are displayed with a version number, date of release, a brief heading, as well as a more detailed description of the new or altered functionality.

Customer config tool

New configuration: Custom mail flow

Customer config tool now allows configuration and maintenance of three types of "Custom mail flow": Internal, ForcedTLS, and AssumeTlsTrue.

The internal mail domains in the Exchange organization are shown in the overview as type Internal. It is crucially important that the DPG solution knows the internal mail domains of the Exchange organization so that the correct secure mail flow can be guaranteed. If internal mail domains are added or deleted in the Exchange organization, they must correspondingly be added or deleted in the overview. If you have any doubts or questions about Internal domains, please contact DPG Service Center.

In rare cases, the TLS verification lookup cannot be completed on the recipient's side for technical reasons, which can result in false negatives. However, this usually does not mean that the recipient domain cannot actually communicate via TLS.

To accommodate those cases, one of two new types can be created: ForcedTLS or AssumeTlsTrue.

• ForcedTLS means that TLS verification lookup¹ is not performed, but TLS sending is enforced, so security is naturally the same. At the same time, the option for S/MIME or tunnel mail is disabled(!) for the specified email addresses or mail domains, so with this type only TLS is enforced for sending. You will most likely prefer to create domains using the AssumeTlsTrue type.
• AssumeTlsTrue means that TLS verification lookup¹ is not performed, but TLS sending is enforced, so security is naturally the same. This type only serves to skip the TLS verification lookup, but will continue to include and prefer S/MIME or tunnel mail as usual in the secure DPG mail flow.

¹ The verification lookup is intended to prevent the user from sending an email from Outlook that will later be stopped in the DPG service.

Improved support for organizations with many Digital Post contact points

To make the list of Digital Post contact points easier to overview, a free text search field for contact points as well as a group filter has been introduced in Customer Config Tool. Additionally, the list can be divided into more manageable sizes.

Additions to DPG REST Customer API

Two new results have been added to the Customer REST API: ProtectedCprMailaddress and CvrName.

ProtectedCprMailaddress is an encrypted version of the recipient email address that can be used for secure sending from the line-of-business system. Use of this feature requires configuration of the DPG service.

CvrName is the organization name of the recipient looked up directly in CVR - the Central Business Register. Connection to CVR is required, as is configuration of the DPG service to use this feature.

Controls for Digital Post and mit.dk

Message size or number of attachments

Before the DPG service sends a Digital Post or mit.dk message to a recipient contact point, the DPG service checks whether there are restrictions on the message size or number of attachments. If one or both are exceeded, the DPG service does not send the message and informs the original sender of the reason.

Information for oversized messages

The DPG solution will now inform directly in a functional mailbox if a Digital Post or mit.dk message is too large compared to the mailbox's Exchange configuration. The information message notes that the functional mailbox must be set up to handle messages up to 150MB.

Redirect to main mailbox for oversized messages

If a functional mailbox's Exchange configuration does not allow receipt of a Digital Post or mit.dk message due to the size of the message, the message is redirected and delivered to the organization's main mailbox. In the message, the DPG solution also informs that the redirect has occurred, so the organization can be aware of it and simultaneously correct the functional mailbox's Exchange configuration so that the functional mailbox can receive messages up to 150MB in the future.

Redirect for oversized messages

If the organization's main mailbox's Exchange configuration does not allow receipt of a Digital Post or mit.dk message due to the size of the message, the message is delivered (after the resend flow for Digital Post or mit.dk is complete) to virk.dk or post.mit.dk respectively. The organization's main mailbox must be set up to handle messages up to 150MB.

Digital Post rate-limiting

To ensure stable operation, Digital Post protects their API with so-called rate-limiting. The DPG solution supports Digital Post rate-limiting, which among other things results in improved system communication during mass delivery.