I think this bug/request and its solution could use a revisit. I'm not
sure about the state of the art in 2013, but in 2021 configuring
OpenDKIM almost any virtual mail server requires a lot more
configuration files. The new two-part signing system does not lend
itself well to just a keys directory and opendkim.conf directly in /etc.
The usual practice is a directory structure as shown:
etc
├── opendkim
| ├── opendkim.conf
| ├── KeyTable
| ├── SigningTable
| ├── TrustedHosts
| ├── Keys
| | ├── domain1.ca
| | | ├── mail.private
| | | ├── mail.txt
| | ├── domain2.ca
| | | ├── mail.private
| | | ├── mail.txt
| | ├── ...
| | |
The original request back in 2013 was to create /etc/opendkim and to
place the config file inside it. This is the standard practice for most
anything that is non-trivial to configure. I would like to request that
this be adopted. Backwards compatibility with the old method can be
maintained by making /etc/opendkim.conf a softlink to
/etc/opendkim/opendkim.conf.
It is telling that I can find no howto or tutorial for OpenDKIM on
Debian that doesn't instruct the user to create /etc/opendkim for
further use:
https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-dkim-with-postfix-on-debian-wheezy
https://allysmith.uk/using-dkim-with-postfix-on-debian
https://meumobi.github.io/sendmail/2015/09/18/install-configure-dkim-sendmail-debian.html
It would be a benefit if OpenDKIM's out-of-the box configuration
structure could match what current practices are in the wild.