DkimX 3.60 Release Notes

Welcome to DkimX 3.60. Please refer to these release notes to obtain the most up-to-date information about installation, documentation, support, and other known issues.

• Release History
• Installing DkimX 3.60
• Upgrading from DkimX 1.x
• Upgrading from DkimX 2.x
• Upgrading from DkimX 3.x
• Updating MS Exchange Server
• Managing DkimX on Windows Server 2019/2022 Server Core installations
• Product Documentation
• Evaluation License
• Technical Support

Release History

v3.60 -/- 2024-02-03:

New or changed features:

• The import of key data, either by using the New-DkimSignerDomainKey cmdlet (Management Shell) or the New Domain Key dialog (Management Console), now also supports files in the legacy PKCS#1 format (.PEM).

Fixed issues:

• The import of PKCS#8 formatted files (.PEM or .DER) containing key data, either by using the New-DkimSignerDomainKey cmdlet (Management Shell) or the New Domain Key dialog (Management Console), does not succeed in circa 20% of all cases.

v3.51 -/- 2022-03-01:

New or changed features:

• None

Fixed issues:

• The Set-VerifierMessageLog cmdlet incorrectly modifies the properties of the DKIM Signer Message Log configuration instead of the Verifier Message Log configuration.

v3.50 -/- 2022-01-14:

New or changed features:

• Centralized management of multiple DkimX instances can optionally be implemented by configuring Inter-Server-Communication.
• A new setting on the DKIM signer can be used to specify whether recipients in custom local domains should be treated by the DKIM signer as external recipients when deciding if a message should be signed or not.

Fixed issues:

• None

v3.20 -/- 2019-01-09:

New or changed features:

• The product now supports MS Exchange Server 2019 on Windows Server 2019 (Server Core & Desktop Experience).

Fixed issues:

• The automatic cleanup of DKIM signer/verifier message log files that are older than the configured maximum age does not work.
• The SPF verifier may fail to evaluate SPF records that contain one or more include mechanisms due to a race condition.

v3.10 -/- 2018-11-02:

New or changed features:

• DKIM signer and DKIM verifier provide support for the signing algorithm Ed25519-SHA256, according to RFC 8463.
• Support for importing a private key from file has changed: The import into an existing DKIM signer domain key object is no longer possible, the Import-DkimSignerDomainKey cmdlet (Management Shell) and the Import Private Key from File Wizard (Management Console) have been removed. The import is now supported at the time of creating a new DKIM signer domain key object, either by using the New-DkimSignerDomainKey cmdlet (Management Shell) or the New Domain Key dialog (Management Console).

Fixed issues:

• The Set-DkimVerifier cmdlet incorrectly rejects valid values for the parameters MinRsaKeySize and MaxRsaKeySize.

v3.0 -/- 2018-06-07:

DkimX 3.0 has been greatly improved compared to previous versions and implements the following main changes:

• Configuration management and resource management is now implemented in a distinct service which runs under the Network Service account.
• Full support for SPF, DKIM and DMARC verification of inbound messages.
• Full support for DMARC reporting.
• Configuration changes are effective immediately. In previous versions configuration changes were cached till being explicitly applied.

Installing DkimX 3.60

Prerequisites for the DkimX feature:

• Windows Server 2012 (R2), Windows Server 2016, Windows Server 2019 (Server Core & Desktop Experience), Windows Server 2022 (Server Core & Desktop Experience).
• MS Exchange Server 2013 with CU21 or a later CU version or MS Exchange Server 2016 with CU11 or a later CU version or MS Exchange Server 2019, either with the Mailbox Server role or the Edge Transport Server role installed.

Note   During installation of DkimX, the service Microsoft Exchange Transport will be restarted.

Note   To create a simple, working DKIM signer configuration after a fresh installation, please follow the steps described in the topic Enable a Local Domain for DKIM Signing.

Note   Though optional, we strongly recommend that you configure one or more recipients of server notifications which will be notified by email of critical errors, license management events and product updates.

Other Installation Considerations

Uninstalling the Product

Note   During uninstallation of DkimX, the service Microsoft Exchange Transport will be restarted.

Upgrading from DkimX 1.x

An in-place upgrade from a DkimX 1.x version to DkimX 3.60 is not supported because DkimX 3.60 can only be installed on MS Exchange 2013/2016/2019 servers while DkimX 1.x versions could only be installed on MS Exchange 2007/2010 servers.

It is possible to perform a one-time migration of your DkimX 1.x configuration: How to Migrate DkimX 1.x/2.x Configuration Settings.

Upgrading from DkimX 2.x

Upgrading from any DkimX 2.x version is supported. All configuration settings will be preserved.

In an in-place upgrade from a DkimX 2.x version is not desired, it is possible to perform a one-time migration of your DkimX 2.x configuration: How to Migrate DkimX 1.x/2.x Configuration Settings.

Upgrading from DkimX 3.x

Upgrading from a previous DkimX 3.x version is supported. All configuration settings will be preserved.

Updating MS Exchange Server

When MS Exchange Server 2013/2016/2019 is updated to the latest cumulative update (CU), the priorities of registered transport agents may be changed, probably resulting in suboptimal functionality of DkimX. We recommend that you check and probably fix the priorities of the DkimX transport agents after updating MS Exchange Server 2013/2016/2019.

Managing DkimX on Windows Server 2019/2022 Server Core installations

To manage a DkimX installation, you can either use the DkimX Management Shell, which provides a command-line interface, or you can use the DkimX Management Console, which provides a graphical user interface (GUI).

On a Windows Server 2019/2022 Server Core installation, to start the DkimX Management Shell you run in the CMD prompt the CMD file LaunchDMS.cmd, located in the directory <InstallDir>\Bin, for example:

"%ProgramFiles%\DkimX\Bin\LaunchDMS.cmd"

To use the DkimX Management Console on a Windows Server 2019/2022 Server Core installation requires installation of the optional feature package Server Core App Compatibility Feature on Demand (FOD). When FOD is installed, MMC 3.0 Snap-Ins, like DkimX Management Console, can be used. To start the DkimX Management Console you run in the CMD prompt the MSC file DkimX.msc, located in the directory <InstallDir>\Bin, for example:

"%ProgramFiles%\DkimX\Bin\DkimX.msc"

Product Documentation

The documentation for the product is available by accessing the DkimX Documentation item in the program group where the product is installed.

Evaluation License

DkimX 3.60 ships with an evaluation license which will expire 60 days after installation.

Technical Support

If you have a technical question about DkimX, use this online documentation or consult Help by clicking the Help button during a procedure. If this doesn't help you, please direct your technical questions to support@netal.com.

Copyright Information

© 2011-2024 Franz Krainer

These materials are provided "as-is", for informational purposes only.

Neither Franz Krainer nor his suppliers makes any warranty, express or implied with respect to the content of these materials or the accuracy of any information contained herein, including, without limitation, the implied warranties of merchantability or fitness for a particular purpose. Because some states/jurisdictions do not allow exclusions of implied warranties, the above limitation may not apply to you.

Neither Franz Krainer nor his suppliers shall have any liability for any damages whatsoever including consequential, incidental, direct, indirect, special, and lost profits. Because some states/jurisdictions do not allow exclusions of implied warranties, the above limitation may not apply to you.

2024-02-03