Public bug reported:
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.
** Affects: opendkim (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697631
Title:
socket path no longer customizable after upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opendkim/+bug/1697631/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
