socket path no longer customizable after upgrade
Bug #1697631 reported by
Jean-Daniel Dupas
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
opendkim (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In opendkim-2.10.3, it was possible to define a custom socket path in /etc/default/
In opendkim-2.11, the systemd.service script has been updated and not only it completely ignore the /etc/default/
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.