ubuntu-mail-server team mailing list archive

[Mikkel Munch Mortensen <1697631@xxxxxxxxxxxxxxxxxx>]

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

** Bug watch added: Debian Bug tracker #864162
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864162

-- 
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:
  Confirmed

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