Ubuntu
opendkim package

OpenDKIM systemd service requires SOCKET in /etc/default/opendkim

Bug #1637636 reported by Jonas Jonsson
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
opendkim (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Running opendkim-2.10.3-3build1.

The Sysv init script, /etc/init.d/opendkim supports reading the Socket option from /etc/opendkim.conf if none could be found in /etc/default/opendkim.

The systemd unit file /lib/systemd/system/opendkim.service on the other hand requires a SOCKET variable in /etc/default/opendkim.

The comment in /etc/default/opendkim suggest that it should work to have it specified in /etc/opendkim.conf instead.

It would be good if the two init scripts behaved in the same way with regards to the configuration.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in opendkim (Ubuntu):
status: New → Confirmed
Revision history for this message
David Bürgin (glts) wrote :

This has been fixed since version 2.11.0~alpha-11 (Ubuntu 18.04).

Now both the systemd and System V init scripts read settings from
/etc/opendkim.conf by default.

Changed in opendkim (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.