The whole issue is with the systemd unit hardcoding the paths, which is
what that patch addresses.
I've been bitten by this as well, and I put a modified systemd unit in
/etc/systemd/system, so as long as this doesn't get fixed any package
upgrades don't break opendmarc.
Stijn
On Tue, 31 Oct 2017 16:11:40 -0700 Jack Bates <3ou...@nottheoilrig.com>
wrote:
> Control: tags -1 patch
>
> I ran into this issue as well -- the following patch fixed it for me:
> http://nottheoilrig.com/options.patch
>
> I copied the default settings from opendmarc.service to
opendmarc.conf
> (PidFile, Socket, and UserID). The administrator can continue to
> override the service, as before (with
> /etc/systemd/system/opendmarc.service.d/override.conf or "systemctl
edit
> opendmarc"). However if they don't, the settings in
/etc/opendmarc.conf
> are respected. Likewise the administrator can continue to configure
the
> SysV init in /etc/default/opendmarc, as before.
>
> Whether or not the administrator has overridden the service, this
change
> won't alter their settings: If the override.conf exists, then it'll
be
> used, same as before. Otherwise the default settings are the same as
before.
>
> When I added the settings to debian/opendmarc.conf I also harmonized
the
> existing settings templates with the upstream opendmarc.conf.sample.
>
>
