Attached you will find a proposed NMU patch that should fix the issue, as suggested by Georges Gouriten.
Note that I kept the -P and -p local: options, since that's how it behaves in sysvinit. Should I upload it? This bug is threatening to kick out of the next Debian stable all reverse dependencies of opendkim, including cyrus-imapd. -- Henrique Holschuh
diff -ru opendkim-2.11.0~alpha.orig/debian/changelog opendkim-2.11.0~alpha/debian/changelog --- opendkim-2.11.0~alpha.orig/debian/changelog 2017-01-25 12:58:07.000000000 -0200 +++ opendkim-2.11.0~alpha/debian/changelog 2017-02-11 14:43:49.482465923 -0200 @@ -1,3 +1,14 @@ +opendkim (2.11.0~alpha-9.1) unstable; urgency=medium + + * Non-maintainer upload. + * Load /etc/opendkim.conf on systemd unit, in the exact same way + we do for the initscript (closes: #853769). Note that overriding + the -P and -p options passed in the command line may require + overriding the systemd unit, but this is exactly as it works in + sysvinit. + + -- Henrique de Moraes Holschuh <h...@debian.org> Sat, 11 Feb 2017 14:40:45 -0200 + opendkim (2.11.0~alpha-9) unstable; urgency=medium * Set umask to 0007 in opendkim.service so opendkim socket is group readable diff -ru opendkim-2.11.0~alpha.orig/debian/opendkim.service opendkim-2.11.0~alpha/debian/opendkim.service --- opendkim-2.11.0~alpha.orig/debian/opendkim.service 2017-01-21 03:45:58.000000000 -0200 +++ opendkim-2.11.0~alpha/debian/opendkim.service 2017-02-11 14:42:03.079269442 -0200 @@ -8,7 +8,7 @@ PIDFile=/var/run/opendkim/opendkim.pid User=opendkim UMask=0007 -ExecStart=/usr/sbin/opendkim -P /var/run/opendkim/opendkim.pid -p local:/var/run/opendkim/opendkim.sock +ExecStart=/usr/sbin/opendkim -x /etc/opendkim.conf -P /var/run/opendkim/opendkim.pid -p local:/var/run/opendkim/opendkim.sock Restart=on-failure ExecReload=/bin/kill -USR1 $MAINPID
