OpenDKIM SOCK path on Debian Jessie

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

OpenDKIM SOCK path on Debian Jessie

danjjde
Hi Friends,

I've set on (Debian Jessie, Posfix 2.11.3-1, Opendkim 2.9.2-2)
/etc/default/opendkim:

SOCKET="local:/var/spool/postfix/var/run/opendkim/opendkim.sock"


and on /etc/postfix/main.cf:

smtpd_milters = unix:/var/run/opendkim/opendkim.sock
non_smtpd_milters = unix:/var/run/opendkim/opendkim.sock

(on opendkim "local" and on posfix "unix" socket)


Apparently all works fine:


systemctl status -l opendkim
● opendkim.service - LSB: Start the OpenDKIM service
    Loaded: loaded (/etc/init.d/opendkim)
    Active: active (running) since lun 2017-10-16 18:27:39 CEST; 2min 31s
ago
   Process: 344 ExecStop=/etc/init.d/opendkim stop (code=exited,
status=0/SUCCESS)
   Process: 349 ExecStart=/etc/init.d/opendkim start (code=exited,
status=0/SUCCESS)
    CGroup: /system.slice/opendkim.service
            ├─356 /usr/sbin/opendkim -x /etc/opendkim.conf -u opendkim -P
/var/run/opendkim/opendkim.pid -p
local:/var/spool/postfix/var/run/opendkim/opendkim.sock
            └─357 /usr/sbin/opendkim -x /etc/opendkim.conf -u opendkim -P
/var/run/opendkim/opendkim.pid -p
local:/var/spool/postfix/var/run/opendkim/opendkim.sock

ott 16 18:27:38 server2 systemd[1]: Starting LSB: Start the OpenDKIM
service...
ott 16 18:27:38 server2 opendkim[344]: Stopping OpenDKIM: opendkim.
ott 16 18:27:39 server2 opendkim[349]: Starting OpenDKIM: opendkim.
ott 16 18:27:39 server2 systemd[1]: Started LSB: Start the OpenDKIM
service.
ott 16 18:27:39 server2 opendkim[357]: OpenDKIM Filter v2.9.2 starting
(args: -x /etc/opendkim.conf -u opendkim -P
/var/run/opendkim/opendkim.pid -p
local:/var/spool/postfix/var/run/opendkim/opendkim.sock)



systemctl status -l postfix
● postfix.service - LSB: Postfix Mail Transport Agent
    Loaded: loaded (/etc/init.d/postfix)
   Drop-In: /run/systemd/generator/postfix.service.d
            └─50-postfix-$mail-transport-agent.conf
    Active: active (running) since lun 2017-10-16 18:27:56 CEST; 2min 4s
ago
   Process: 365 ExecStop=/etc/init.d/postfix stop (code=exited,
status=0/SUCCESS)
   Process: 389 ExecStart=/etc/init.d/postfix start (code=exited,
status=0/SUCCESS)
    CGroup: /system.slice/postfix.service
            ├─508 /usr/lib/postfix/master
            ├─509 pickup -l -t unix -u -c
            ├─510 qmgr -l -t unix -u
            ├─514 smtpd -n smtp -t inet -u -c -o stress= -s 2
            ├─515 proxymap -t unix -u
            ├─516 tlsmgr -l -t unix -u -c
            └─517 anvil -l -t unix -u -c

ott 16 18:27:56 server2 postfix[389]: Starting Postfix Mail Transport
Agent: postfix.



I would like to know if this (opendkim "local" and posfix "unix" socket)
is correct or if it could generate any problems.



Many many thanks!

Davide


Reply | Threaded
Open this post in threaded view
|

Re: OpenDKIM SOCK path on Debian Jessie

A. Schulze


Am 16.10.2017 um 18:51 schrieb Davide Marchi:
> SOCKET="local:/var/spool/postfix/var/run/opendkim/opendkim.sock"
vs.
> smtpd_milters = unix:/var/run/opendkim/opendkim.sock
> non_smtpd_milters = unix:/var/run/opendkim/opendkim.sock

postfix and sendmail/milter use different notation to describe the same socket location.

http://www.postfix.org/MILTER_README.html#smtp-only-milters
vs.
http://opendkim.org/opendkim.conf.5.html (search for "Socket" ...)

to me your setup looks fine...
Andreas
Reply | Threaded
Open this post in threaded view
|

Re: OpenDKIM SOCK path on Debian Jessie

danjjde
Il 2017-10-16 19:07 A. Schulze ha scritto:

> [..]
> postfix and sendmail/milter use different notation to describe the
> same socket location.
>
> http://www.postfix.org/MILTER_README.html#smtp-only-milters
> vs.
> http://opendkim.org/opendkim.conf.5.html (search for "Socket" ...)
>
> to me your setup looks fine...
> Andreas

Hi Andreas and thanks very very much for your help!
Very useful your information!
Of course, if the developers adopted a single standard would not be bad
and it would save users a lot of time :-D

I've read many tutorials that do not keep track of this difference, I
will write to the some editors.

Thanks again!


Davide