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
Feat/enable custom dkim selector #1811
Feat/enable custom dkim selector #1811
Conversation
Anyone has documentation for running test locally? |
There's this thing, you know, called CONTRIBUTING.md. I assume you've not read it... Your addition is very welcome. But the way you've done it cannot work. You're using the selector as @wernerfred I thought about another way of parsing the arguments. I will explain in a few minutes in this thread. |
From my PoV, the script should work like this: SYNOPSIS
./setup.sh dkim [OPTIONS...]
DESCRIPTION
Configures DKIM keys. OPTIONS can be used to configure a more complex setup. LDAP setups require these options.
OPTIONS
Generic Program Information
help Print the usage information.
Configuration adjustments
size Set the size of the keys to be generated. Possible are 1024, 2024 (default) and 4096.
selector Set a manual selector (default is "mail") for the key.
domains Provide the domains for which keys are to be generated.
This adheres to a man-page style. I will provide a PR. This is a breaking change, but with the upcoming merge of #1802 and release @astrocket I will then leave it up to you to rebase and implement the new selector feature of course :D |
I really like your approach. When I "hotfixed" the script I had no time to do a complete refactor. Your change will require many changes to tests too. Hit me up if you need support. If you use a branch and not a fork I can contribute too (maybe then it is also time to get rid of this ugly Regarding |
@aendeavor Thanks a lot :) I hope I can follow up. |
I will open a PR with on a branch and assign you too :D
Most definitely.
@astrocket We will get back to you once we're finished. Until then, I will mark this as a draft. |
@wernerfred There is the new |
@astrocket #1812 was merged. You can go ahead and rebase on Please note: Your script adjustments were fine. But the issue #1304 features a TODO list which is longer:
|
Just for our (the maintainers) information: How long do you think it will take you to make this PR ready for merge @astrocket ? |
18bc2ac
to
7815119
Compare
I rebased the pr branch as the modified files were all splitted in new files in the meantime. |
Tests currently failing:
EDIT: actually the tests checked the existence of 4 domains but only one is added in test setup. Removed the 3 obsolete domains
|
LGTM 👍🏼 Ready for merge I guess :D |
1, 2, 4 and 5 ist done. What needs to be done with 3? |
I guess maybe docker-mailserver/target/scripts/start-mailserver.sh Lines 1105 to 1135 in 9efa94c
needs adjustments? I can't see any, but that doesn't mean they don't exist... PS: Although this function could also use some love, and could be shortened down a bit. |
@astrocket did you test my changes again? |
What do you think of changing this: docker-mailserver/target/scripts/start-mailserver.sh Lines 1105 to 1135 in 9efa94c
to this:
Imho no need to:
If nothing speaks against this change I will commit and merge |
If these changes work, go ahead :D |
Description
Enable generate-dkim-config to accept selector as third parameter.
which will apply to
private key generation
,key names
,KeyTable
,SigningTable
Fixes #1304
Type of change
Checklist: