From c1cf41dcb3a51abb5bfb03d2151472ed940876cd Mon Sep 17 00:00:00 2001 From: fim-sh <211835880+fim-sh@users.noreply.github.com> Date: Wed, 23 Jul 2025 10:52:58 +0000 Subject: [PATCH] move restart required to both odkim and rspamd --- docs/content/config/best-practices/dkim_dmarc_spf.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/content/config/best-practices/dkim_dmarc_spf.md b/docs/content/config/best-practices/dkim_dmarc_spf.md index 730b3520..a1531992 100644 --- a/docs/content/config/best-practices/dkim_dmarc_spf.md +++ b/docs/content/config/best-practices/dkim_dmarc_spf.md @@ -120,9 +120,6 @@ DKIM is currently supported by either OpenDKIM or Rspamd: After running `setup config dkim`, your new DKIM key files (_and OpenDKIM config_) have been added to `/tmp/docker-mailserver/opendkim/`. - !!! info "Restart required" - - After restarting DMS, outgoing mail will now be signed with your new DKIM key(s) :tada: === "Rspamd" @@ -224,6 +221,10 @@ DKIM is currently supported by either OpenDKIM or Rspamd: If there is a mismatch, a warning will be emitted to the Rspamd log `/var/log/mail/rspamd.log`. +!!! info "Restart required" + + After restarting DMS, outgoing mail will now be signed with your new DKIM key(s) :tada: + ### DNS Record { #dkim-dns } When mail signed with your DKIM key is sent from your mail server, the receiver needs to check a DNS `TXT` record to verify the DKIM signature is trustworthy.