Skip to content
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

[enhancement]: DKIM Rotation #1106

Open
1 task done
nomadturk opened this issue Jan 19, 2025 · 2 comments
Open
1 task done

[enhancement]: DKIM Rotation #1106

nomadturk opened this issue Jan 19, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@nomadturk
Copy link

Which feature or improvement would you like to request?

I'd like to see this feature:

The way stalwart is built at the moment, there is a single set of DKIM keys, with no way to change, reissue them.

It would be great if we can create multiple DKIM rsa keys per domain, and were able rotate them an API call by making another key the main, making the older one obsolete.

And with another API endpoint, if we can delete/renew the old one, that would give us the ability to rotate DKIM keys while another one is being used.

Is your feature request related to a problem?

I'm having a problem with...

Code of Conduct

  • I agree to follow this project's Code of Conduct
@nomadturk nomadturk added the enhancement New feature or request label Jan 19, 2025
@andreymal
Copy link

Duplicate of #368?

Right now you can create/edit/delete DKIM keys using POST /api/settings, although it's a bit inconvenient

@nomadturk
Copy link
Author

Looks like it is really similar @andreymal
And I also have a vote there ^_^

But I would be opposed to automatic rotation. And this feature shouldn't be tied to TLS-DNS-01. Stalwart does not and can not manage the DNS for all clients.

And another difference is, I would like to see at least 2 different keys, during time of domain creation.
Only one should be active and disabling one and enabling the other would give seamless rotation capability without having to mess with DNS all the time. And once they are present, this could be as easy as calling a switch key endpoint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants