[GH-ISSUE #58] Configuration not accepted with version 2.0 #42

New issue

Closed

opened 2026-02-26 10:35:21 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 10:35:21 +03:00

Owner

Originally created by @psdogado on GitHub (Aug 25, 2014).
Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/58

Hi,

I've upgraded our Exchange platform to CU5, so i needed to upgrade the transport agent to 2.0 beta 3.
It seems, that no dkim signatures are appended anymore to my mails. the event log shows "Exchange DKIM settings loaded: RsaSha1, Canonicalization Header Algorithm: Relaxed, Canonicalization Body Algorithm: Relaxed, Number of domains: 0". Why is my configuration (which works with 1.8.3) not accepted with the new agent version?
Btw. I did not install the agent with the installer (error path2 etc), but used the install.ps1.

Kind regards,
Peter

Originally created by @psdogado on GitHub (Aug 25, 2014). Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/58 Hi, I've upgraded our Exchange platform to CU5, so i needed to upgrade the transport agent to 2.0 beta 3. It seems, that no dkim signatures are appended anymore to my mails. the event log shows "Exchange DKIM settings loaded: RsaSha1, Canonicalization Header Algorithm: Relaxed, Canonicalization Body Algorithm: Relaxed, Number of domains: 0". Why is my configuration (which works with 1.8.3) not accepted with the new agent version? Btw. I did not install the agent with the installer (error path2 etc), but used the install.ps1. Kind regards, Peter

kerem closed this issue

2026-02-26 10:35:22 +03:00

kerem commented

2026-02-26 10:35:22 +03:00

Author

Owner

@Pro commented on GitHub (Aug 25, 2014):

We had to change the format of the configuration file, therefore the config from 1.8.3 doesn't work in version 2.0. Thus the agent loads the default config which contains no domains. You can use the Configuration.DkimSigner.exe to create a new config file for version 2. It should work regardless your mentioned error (path2, #47). If not, you have to edit the config file manually.
It should be located under C:\Program Files\Exchange DkimSigner\settings.xml and here is an example content (replace it with your domain settings):

<?xml version="1.0" encoding="utf-8"?>
<Settings xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Loglevel>3</Loglevel>
  <SigningAlgorithm>RsaSha1</SigningAlgorithm>
  <HeaderCanonicalization>Relaxed</HeaderCanonicalization>
  <BodyCanonicalization>Relaxed</BodyCanonicalization>
  <HeadersToSign>
    <string>From</string>
    <string>Subject</string>
    <string>To</string>
    <string>Date</string>
    <string>Message-ID</string>
  </HeadersToSign>
  <Domains>
    <DomainElement>
      <Domain>example.com</Domain>
      <Selector>ex201302</Selector>
      <PrivateKeyFile>keys\example.com\ex201302.private</PrivateKeyFile>
    </DomainElement>
    <DomainElement>
      <Domain>example.org</Domain>
      <Selector>ex201302</Selector>
      <PrivateKeyFile>keys\example.org\ex201302.private</PrivateKeyFile>
    </DomainElement>
  </Domains>
</Settings>

The install.ps1 script is not yet adapted to the new version therefore it shouldn't be used. Sorry for the mess, we currently don't have much time to work on the DKIM signer. I hope I can fix the script and install process in the next days so we can finally release version 2.0.0

@Pro commented on GitHub (Aug 25, 2014): We had to change the format of the configuration file, therefore the config from 1.8.3 doesn't work in version 2.0. Thus the agent loads the default config which contains no domains. You can use the Configuration.DkimSigner.exe to create a new config file for version 2. It should work regardless your mentioned error (path2, #47). If not, you have to edit the config file manually. It should be located under `C:\Program Files\Exchange DkimSigner\settings.xml` and here is an example content (replace it with your domain settings): ``` xml <?xml version="1.0" encoding="utf-8"?> <Settings xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Loglevel>3</Loglevel> <SigningAlgorithm>RsaSha1</SigningAlgorithm> <HeaderCanonicalization>Relaxed</HeaderCanonicalization> <BodyCanonicalization>Relaxed</BodyCanonicalization> <HeadersToSign> <string>From</string> <string>Subject</string> <string>To</string> <string>Date</string> <string>Message-ID</string> </HeadersToSign> <Domains> <DomainElement> <Domain>example.com</Domain> <Selector>ex201302</Selector> <PrivateKeyFile>keys\example.com\ex201302.private</PrivateKeyFile> </DomainElement> <DomainElement> <Domain>example.org</Domain> <Selector>ex201302</Selector> <PrivateKeyFile>keys\example.org\ex201302.private</PrivateKeyFile> </DomainElement> </Domains> </Settings> ``` The install.ps1 script is not yet adapted to the new version therefore it shouldn't be used. Sorry for the mess, we currently don't have much time to work on the DKIM signer. I hope I can fix the script and install process in the next days so we can finally release version 2.0.0

kerem commented

2026-02-26 10:35:22 +03:00

Author

Owner

@psdogado commented on GitHub (Aug 25, 2014):

It seems to work now, thanks !
The above xml file references at "PrivateKeyFile" the path "keys\example.org..", but it seems like the agent also prefixes the path with keys. with your config it generates the event "Private Key not found: C:\Program Files\Exchange DkimSigner\keys\keys\st...". So after stripping the keys\ fronm the settings.xml all domains are found.

@psdogado commented on GitHub (Aug 25, 2014): It seems to work now, thanks ! The above xml file references at "PrivateKeyFile" the path "keys\example.org..", but it seems like the agent also prefixes the path with keys. with your config it generates the event "Private Key not found: C:\Program Files\Exchange DkimSigner\keys\keys\st...". So after stripping the keys\ fronm the settings.xml all domains are found.