You are not logged in.

#1 2020-09-10 04:55:27

gerodot
Member
Registered: 2020-09-10
Posts: 1

OpenDKIM -- doesn't work via unix sockets

I want to make OpenDKIM work via unix socket. I've read the instructions in the wiki and they haven't worked for me:


# /etc/opendkim/opendkim.conf


# (1) Socket "local:/var/spool/postfix/opendkim/opendkim.sock"
# (2) Socket local:/run/opendkim/opendkim.sock
# (3) Socket local:/var/spool/postfix/var/run/opendkim/opendkim.sock

Socket                  inet:8891@localhost # only this works

but I don't want to use network sockets.

(1) -> OpenDKIM Filter: unknown socket type "local"; Unable to create listening socket on conn "local"; smfi_opensocket() failed

(2) -> "Unable to bind to port local:/run/opendkim/opendkim.sock: No such file or directory; Unable to create listening socket on conn local:/run/opendkim/opendkim.sock"

(3) -> "Unable to bind to port local:/var/spool/postfix/var/run/opendkim/opendkim.sock: No such file or directory; Unable to create listening socket on conn local:/var/spool/postfix/var/run/opendkim/opendkim.sock"


Do I have to create a file for a unix socket first? Why has that not been mentioned in the wiki? The instructions in the wiki are incorrect.

Last edited by gerodot (2020-09-10 04:58:39)

Offline

#2 2020-09-10 10:16:38

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,371

Re: OpenDKIM -- doesn't work via unix sockets

Care to point to the incorrect section? I only see the specific socket on /run being mentioned in the security section where it is accompanied by a systemd service that will if properly setup ensure that these directories exist.

No mention of /var/spool in any case, are you looking at a localized page?

But generally yes you need to ensure that the directory you plan to plant your socket in exists and has the correct permissions. But I don't see anything that's in the normal english wiki contradicts this in any form .

Last edited by V1del (2020-09-10 10:32:08)

Offline

Board footer

Powered by FluxBB