socket path no longer customizable after upgrade

[Jean-Daniel Dupas]

In opendkim-2.10.3, it was possible to define a custom socket path in /etc/default/opendkim and the systemd.service file was loading it and using it to define a custom socket path.

In opendkim-2.11, the systemd.service script has been updated and not only it completely ignore the /etc/default/opendkim, but it also hardcode the socket path without providing any way to change it, which is a requirement to use opendkim with postfix, as the later is chrooted.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mikkel Munch Mortensen (3xm)]

I believe this bug has been inherited from Debian, where it was fixed on Sep. 24th 2017 [1]. I don't know how the process of getting updated packages from Debian into Ubuntu, but to me it seems like an easy task for someone with the proper knowledge and permissions.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864162

[David Bürgin (glts)]

The systemd opendkim service no longer reads /etc/default/opendkim. This has been the case since version 2.11.0~alpha-8 (Ubuntu 18.04).

As it is, there are two alternative ways to customise these settings:

- Option 1:
  * Set desired options in /etc/default/opendkim
  * Execute `/lib/opendkim/opendkim.service.generate` (this generates systemd drop-in configuration at /etc/systemd/system/opendkim.service.d/override.conf derived from /etc/default/opendkim)
  * Execute `systemctl daemon-reload && systemctl restart opendkim`
- Option 2: Set desired options directly in /etc/opendkim.conf

Option 2 is preferred, but either one of these approaches allow you to configure PID and socket for the Postfix chroot.