[GH-ISSUE #121] Verify private key in DKIM configurator #97

Closed
opened 2026-02-26 10:35:54 +03:00 by kerem · 5 comments
Owner

Originally created by @matbech on GitHub (Jan 3, 2016).
Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/121

Originally assigned to: @Pro on GitHub.

The configuration should verify the private key file (.pem) assigned to each domain. This helps identifying incorrect private key as early as possible and prevents possible crashes in the DKIM transport agents later.

Originally created by @matbech on GitHub (Jan 3, 2016). Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/121 Originally assigned to: @Pro on GitHub. The configuration should verify the private key file (.pem) assigned to each domain. This helps identifying incorrect private key as early as possible and prevents possible crashes in the DKIM transport agents later.
kerem 2026-02-26 10:35:54 +03:00
Author
Owner

@Pro commented on GitHub (Jan 3, 2016):

The configurator already checks for valid private keys (see https://github.com/Pro/dkim-exchange/blob/master/Src/Configuration.DkimSigner/MainWindow.cs#L961). The check is performed when you use the Select key file button.
This is exactly the same parser/code which the signer uses.
Can you make sure that you are using the 3.0.0-beta version of the configurator. Does it show any error message?

<!-- gh-comment-id:168493641 --> @Pro commented on GitHub (Jan 3, 2016): The configurator already checks for valid private keys (see https://github.com/Pro/dkim-exchange/blob/master/Src/Configuration.DkimSigner/MainWindow.cs#L961). The check is performed when you use the `Select key file` button. This is exactly the same parser/code which the signer uses. Can you make sure that you are using the 3.0.0-beta version of the configurator. Does it show any error message?
Author
Owner

@matbech commented on GitHub (Jan 3, 2016):

Yes I'm using the configurator from 3.0.0-beta and no error is displayed after I selected the private key with the select button.

<!-- gh-comment-id:168493792 --> @matbech commented on GitHub (Jan 3, 2016): Yes I'm using the configurator from 3.0.0-beta and no error is displayed after I selected the private key with the select button.
Author
Owner

@Pro commented on GitHub (Jan 3, 2016):

Ok, can you try out the newly compiled dll from here:
https://github.com/Pro/dkim-exchange/tree/master/Src/Exchange.DkimSigner/bin

Download all the files in the corresponding directory for your Exchange server. Then copy the files to C:\Program Files\Exchange DKIM\ and replace if asked. (You may need to stop the Microsoft Exchange Transport service to be able to overwrite them).

Then, when you start the Transport service, do you see any error in the Event Log?

<!-- gh-comment-id:168494119 --> @Pro commented on GitHub (Jan 3, 2016): Ok, can you try out the newly compiled dll from here: https://github.com/Pro/dkim-exchange/tree/master/Src/Exchange.DkimSigner/bin Download all the files in the corresponding directory for your Exchange server. Then copy the files to `C:\Program Files\Exchange DKIM\` and replace if asked. (You may need to stop the `Microsoft Exchange Transport` service to be able to overwrite them). Then, when you start the Transport service, do you see any error in the Event Log?
Author
Owner

@matbech commented on GitHub (Jan 3, 2016):

"Could not initialize MimeKit DkimSigner for domain abcd.com: Private key not found."

The private key file has been selected in the configurator and is located at:
C:\Program Files\Exchange DkimSigner\keys\abcd.com.pem

The settings.xml:

<DomainElement>
<Domain>abcd.com</Domain>
<Selector>mail</Selector>
<PrivateKeyFile>abcd.com.pem</PrivateKeyFile>
</DomainElement>
</Domains>
<!-- gh-comment-id:168494620 --> @matbech commented on GitHub (Jan 3, 2016): "Could not initialize MimeKit DkimSigner for domain abcd.com: Private key not found." The private key file has been selected in the configurator and is located at: C:\Program Files\Exchange DkimSigner\keys\abcd.com.pem The settings.xml: ``` <Domains> <DomainElement> <Domain>abcd.com</Domain> <Selector>mail</Selector> <PrivateKeyFile>abcd.com.pem</PrivateKeyFile> </DomainElement> </Domains> ```
Author
Owner

@Pro commented on GitHub (Jan 3, 2016):

The check expected the wrong PEM key format. It should now be fixed.
Please try again and let me know if there are any errors:
https://github.com/Pro/dkim-exchange/tree/master/Src/Exchange.DkimSigner/bin

<!-- gh-comment-id:168498954 --> @Pro commented on GitHub (Jan 3, 2016): The check expected the wrong PEM key format. It should now be fixed. Please try again and let me know if there are any errors: https://github.com/Pro/dkim-exchange/tree/master/Src/Exchange.DkimSigner/bin
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dkim-exchange-Pro#97
No description provided.