-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Replace opendkim with dkimpy #2220
base: main
Are you sure you want to change the base?
Conversation
Can the existing DKIM keys (mail.private and mail.txt) be re-used instead of creating new ones? This might avoid some trouble especially for those using third-party dns. |
That's a good point. When I configured this I made it so that I could easily switch it with the old situation, including changing the selector, port number etc. I did not think about the migration situation anymore. |
Not yet tested. |
Tested as follows:
Both installations were able to sign and verify the rsa and the ed25519 keys. Looks good to me. |
This pull request migrates the current usage of OpenDKIM to dkimpy. OpenDKIM did not have any upstream releases for a long time, and might be considered no longer maintained. Dkimpy seems a good replacement.
Changes:
dkimpy also supports ARC (RFC 8617 Authenticated Received Chain), but this pull request does nothing with that.
Tested by spinning up a box with this branch, then sending and receiving email from and to the box. Both signing and verifying of both dkim signatures (rsa and ed25519) are working.
Thanks to https://colincogle.name/blog/replacing-opendkim/ for inspiration for these changes.