-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configuration not accepted with version 2.0 #58
Comments
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. <?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 |
It seems to work now, thanks ! |
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
The text was updated successfully, but these errors were encountered: