Your message dated Thu, 23 Jan 2020 15:42:25 +0100
with message-id <[email protected]>
and subject line opendkim: Breaks with Debians unbound config
has caused the Debian Bug report #849322,
regarding opendkim: Breaks with Debians unbound config
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 [email protected]
immediately.)


-- 
849322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849322
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: opendkim
Version: 2.9.2-2
Severity: important

Dear Maintainer,

as subject says, opendkim does not like Debians unbound, when using the
ResolverConfiguration option.

By default Debians unbound.conf only contains a line

include: "/etc/unbound/unbound.conf.d/*.conf"

and opendkim breaks with

Dec 25 13:09:14 vir opendkim[22357]: can't configure DKIM library: failed to 
add resolver configuration file

which isn't nice of it.
Replace the config with a full unbound.conf and it works.
Simply add the include line, and it breaks, so it probably "just"
doesn't like the input statement?

-- 
bye, Joerg

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
This is not reproducible today, no such error message appears.

What is true even today, though, is that the unbound.conf configuration
files shipped with the unbound package are not compatible with opendkim,
but for a different reason. Specifically,
/etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf contains a
setting for parameter ‘auto-trust-anchor-file’ which is only really
suitable for the standalone unbound service, not for the libunbound
instance in opendkim, because of an owner permissions mismatch.

I have documented this in the wiki at https://wiki.debian.org/opendkim.

As this issue is not reproducible in the stated form today, ie the
include syntax is working well, I’m closing the bug.

--- End Message ---

Reply via email to