# grep -R Trust mail-filter/opendkim/ mail-filter/opendkim/opendkim-2.9.1.ebuild: echo TrustedAnchorFile /etc/dnssec/root-anchors.txt >> "${D}"/etc/opendkim/opendkim.conf mail-filter/opendkim/opendkim-2.8.4.ebuild: echo TrustedAnchorFile /etc/dnssec/root-anchors.txt >> "${D}"/etc/opendkim/opendkim.conf mail-filter/opendkim/opendkim-2.8.3.ebuild: echo TrustedAnchorFile /etc/dnssec/root-anchors.txt >> "${D}"/etc/opendkim/opendkim.conf mail-filter/opendkim/opendkim-2.9.0.ebuild: echo TrustedAnchorFile /etc/dnssec/root-anchors.txt >> "${D}"/etc/opendkim/opendkim.conf # /etc/init.d/opendkim start * Caching service dependencies ... [ ok ] * Starting OpenDKIM ... opendkim: /etc/opendkim/opendkim.conf: configuration error at line 20: unrecognized parameter * start-stop-daemon: failed to start `/usr/sbin/opendkim' [ !! ] * ERROR: opendkim failed to start I'd rearranged the opendkim.conf file by this time, but line 20 read: TrustedAnchorFile /etc/dnssec/root-anchors.txt ... however, the man page from v2.8.4 states: TrustAnchorFile (string) Specifies a file from which trust anchor data should be read when doing DNS queries and applying the DNSSEC protocol. This is currently ignored unless the underlying library is compiled to use Unbound; see the documentation at at [sic] http://unbound.net for the expected format of this file. ... and indeed, removing the 'ed' and so changing 'TrustedAnchorFile' to 'TrustAnchorFile' allows opendkim to start.
Fixed in CVS. Thanks for the report.
