📝 Preliminary Checks

• I tried searching for an existing issue and followed the debugging docs advice, but still need assistance.

👀 What Happened?

Hi

when using rspamd for DKIM output signing, two steps are involved

1. generating the keys with docker exec -it <CONTAINER NAME> setup config dkim
2. add the path to the key to the config file config/rspamd/override.d/dkim_signing.conf

When running step 1 at the end rspamd is restarted (which may be necessary for dkim input verification) but doc is missing the information that after step 2 the container needs to be restarted.

I think restarting rspamd only is not enough because it doesn't not update /etc/rspamd/override.d/dkim_signing.conf inside the container.

If this issue is pertinent, I can propose a PR to update the doc.

👟 Reproduction Steps

• add a new mailbox with a new domain
• generate its DKIM key with the setup tool
• add the path to the key inside config/rspamd/override.d/dkim_signing.conf
• send a mail from this new mailbox to the outside and verify if it's DKIM-signed

🐋 DMS Version

v15.0

💻 Operating System and Architecture

Debian 12.9, amd64

⚙️ Container configuration files

📜 Relevant log output