Your message dated Mon, 20 Feb 2017 00:03:26 -0500
with message-id <5334532.MmRNLRdGih@kitterma-e6430>
and subject line Re: opendkim: Default systemd service does not read the
configuration file
has caused the Debian Bug report #853769,
regarding opendkim: Default systemd service does not read the configuration file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
853769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opendkim
Version: 2.11.0~alpha-8
Severity: important
Dear Maintainer,
I installed opendkim on a new server and had a problem, /etc/opendkim.conf was
not read with "service opendkim start".
I fixed it by changing a line in /lib/systemd/system/opendkim.service
-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
The default does not seem convenient to me.
Best regards
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Tue, 31 Jan 2017 18:48:26 +0100 Georges Gouriten <geor...@gouriten.name>
wrote:
> Source: opendkim
> Version: 2.11.0~alpha-8
> Severity: important
>
> Dear Maintainer,
>
> I installed opendkim on a new server and had a problem, /etc/opendkim.conf
was not read with "service opendkim start".
>
> I fixed it by changing a line in /lib/systemd/system/opendkim.service
>
> -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
>
> The default does not seem convenient to me.
I've finally had time to investigate and test this claim and it is not
correct. As stated in the opendkim man page, the default config file is
/etc/opendkim.conf, so there is no need to specify it.
Using the existing service file I confirmed that changes in /etc/opendkim.conf
do affect the configuration of the running service after it is restarted.
There's no change needed.
Scott K
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
