📝 Preliminary Checks
👀 What Happened?
Well this is not really a bug as this does not impact DMS operation. The following warning message is emitted at startup when using a Rspamd path syntax using the $domain and $selector variables (see Rspamd configuration or PR #3702 that documents it):
Rspamd DKIM private key file '/tmp/docker-mailserver/rspamd/dkim/$domain/$selector.private' is configured for usage, but does not appear to exist
It could be nice not to emit such message.
Our dkim_signing.conf file contains the following line:
path = "/tmp/docker-mailserver/rspamd/dkim/$domain/$selector.private";
From what I found in the code, it seems to come from the __rspamd__check_dkim_permissions() function.
👟 Reproduction Steps
No response
🐋 DMS Version
v14.0.0
💻 Operating System and Architecture
Debian 12
⚙️ Container configuration files
No response
📜 Relevant log output
No response
Improvements to this form?
No response
📝 Preliminary Checks
👀 What Happened?
Well this is not really a bug as this does not impact DMS operation. The following warning message is emitted at startup when using a Rspamd
pathsyntax using the$domainand$selectorvariables (see Rspamd configuration or PR #3702 that documents it):It could be nice not to emit such message.
Our
dkim_signing.conffile contains the following line:From what I found in the code, it seems to come from the
__rspamd__check_dkim_permissions()function.👟 Reproduction Steps
No response
🐋 DMS Version
v14.0.0
💻 Operating System and Architecture
Debian 12
⚙️ Container configuration files
No response
📜 Relevant log output
No response
Improvements to this form?
No response