📝 Preliminary Checks
👀 What Happened?
When setup config dkim is used with rspam, the configuration is put into /etc/rspamd/override.d/dkim_signing.conf.
That location is not persisted, it would be better to put it directly into /tmp/docker-mailserver/rspamd/override.d/dkim_signing.conf. This was annoying to find as it was only visible after a restart of the container.
This could be seen either as incomplete documentation or suboptimal behavior of the setup script.
I'd prefer if the script handles it better as it already creates the keys in the persistent location.
👟 Reproduction Steps
- Set
ENABLE_RSPAMD=1 and ENABLE_OPENDKIM=0.
- Run
setup config dkim.
- Notice the path setup for the default configuration.
🐋 DMS Version
:edge as of October 18
💻 Operating System and Architecture
SuSE MicroOS
⚙️ Container configuration files
Default compose.yaml
📜 Relevant log output
[ INF ] Supplying a default configuration ('/etc/rspamd/override.d/dkim_signing.conf')
📝 Preliminary Checks
👀 What Happened?
When
setup config dkimis used with rspam, the configuration is put into/etc/rspamd/override.d/dkim_signing.conf.That location is not persisted, it would be better to put it directly into
/tmp/docker-mailserver/rspamd/override.d/dkim_signing.conf. This was annoying to find as it was only visible after a restart of the container.This could be seen either as incomplete documentation or suboptimal behavior of the setup script.
I'd prefer if the script handles it better as it already creates the keys in the persistent location.
👟 Reproduction Steps
ENABLE_RSPAMD=1andENABLE_OPENDKIM=0.setup config dkim.🐋 DMS Version
:edgeas of October 18💻 Operating System and Architecture
SuSE MicroOS
⚙️ Container configuration files
Default
compose.yaml📜 Relevant log output