ns8-mail should also mount a /etc/rspamd/local.d volume next to /etc/rspamd/override.d to allow addition/simple changes instead of whole section overwrites

[jmartens]

I want to be able to fully leverage the rspamd override and extension mechanism to add or change configuration directives. Current option seems to be to fully override complete sections, where the subtlety of the rspamd override mechanism has also an option to add to /etc/rspamd/local.d which then gets merged into the default configuration as is shown at https://docs.rspamd.com/faq/#what-is-the-difference-between-locald-and-overrided

Proposed solution

Also mount a volume to /etc/rspamd/local.d comparable to /etc/rspamd/override.d

Alternative solutions

Full overrides which I don't preffer since for some options there is a much more simple and less invasive approach.

Additional context

Context is that I want to exclude a single sender from a lua policy module and is not affected by normal whitelist files, the ones listed in rspamd configuration tab. I want to do this to make a specific host excluded from the pretty harsh ONCE_RECEIVED_STRICT policy.

See also

My quest on the NethSevrer community and the rspamd FAQ on the difference between /etc/rspamd/local.d and /etc/rspamd/override.d

And specific for my case: RSPAMD once_received configuration options

[DavidePrincipi]

By design, override.d/ is mapped to a persistent volume to allow admins to apply advanced customizations that must survive container restarts and upgrades.

We do not also map local.d/, because that directory is part of the container image and is used to ship the Mail module’s default Rspamd configuration. Exposing it as a writable volume would blur the separation between upstream-provided configuration and user overrides.

This is a deliberate trade-off between preserving the upstream configuration structure and the Mail module’s container-based architecture, while still providing a supported and persistent customization path through override.d/.