← Back to team overview

ubuntu-mail-server team mailing list archive

[Bug 1697631] Re: socket path no longer customizable after upgrade

 

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.

** Changed in: opendkim (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Mail Server, which is subscribed to opendkim in Ubuntu.
https://bugs.launchpad.net/bugs/1697631

Title:
  socket path no longer customizable after upgrade

Status in opendkim package in Ubuntu:
  Fix Released

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opendkim/+bug/1697631/+subscriptions


References