[Bug 230685] mail/opendkim fails to start when socket directory /var/run/milteropendkim has group write acl

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Aug 17 06:39:10 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230685

            Bug ID: 230685
           Summary: mail/opendkim fails to start when socket directory
                    /var/run/milteropendkim has group write acl
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: dewayne at heuristicsystems.com.au
                CC: freebsd-ports at dan.me.uk
                CC: freebsd-ports at dan.me.uk
             Flags: maintainer-feedback?(freebsd-ports at dan.me.uk)

The /usr/local/etc/rc.d/milter-opendkim is really very good, thankyou.  However
I experience startup failures which sendmail advises via its maillog:
Aug 17 13:47:11 b3 sm-mta[4193]: w7H3lB78004193: Milter (dkim): local socket
name /var/run/milteropendkim/sock unsafe

Gasp!

sendmail doesn't like group write permissions on /var/run/milteropendkim/.

FIX
Modifying all instances of "_piddir_perms=" in the startup rc file, to
_piddir_perms="0750"
fixes the issue.  

And for package builds, the same step needs to be applied to 
/usr/ports/mail/opendkim/files/milter-opendkim.in

BACKGROUND
My env is FreeBSD11.2, the rc.conf entries are
milteropendkim_enable="YES"
milteropendkim_uid="dkim"
milteropendkim_cfgfile="/usr/local/etc/opendkim.conf"
milteropendkim_socket="/var/run/milteropendkim/sock"

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list