opendkim Service unavailable

**web4you** · Jul 10th 2017

After upgrade to 4.1.7 (but also in 4.1.6) i get the following error in /var/log/mail.log

Code

After restart opendkim/var/log/mail.logJul 10 08:28:30 web4you-server-02 dovecot: master: Dovecot v2.2.27 (c0f36b0) starting up for imap, sieve, pop3 (core dumps disabled)Jul 10 08:29:15 web4you-server-02 opendkim[13151]: OpenDKIM Filter v2.11.0 starting (args: -P /var/run/opendkim/opendkim.pid -p local:/var/run/opendkim/opendkim.sock)and after "sending" emailJul 10 08:31:00 web4you-server-02 postfix/smtpd[13440]: connect from 203-18-138-91.dyn.cable.fcom.ch[91.138.18.203]Jul 10 08:31:00 web4you-server-02 postfix/smtpd[13440]: warning: connect to Milter service unix:/opendkim/opendkim.sock: No such file or directoryJul 10 08:31:00 web4you-server-02 postfix/smtpd[13440]: NOQUEUE: milter-reject: CONNECT from 203-18-138-91.dyn.cable.fcom.ch[91.138.18.203]: 451 4.7.1 Service unavailable - try again later; proto=SMTPJul 10 08:31:00 web4you-server-02 postfix/smtpd[13440]: NOQUEUE: milter-reject: EHLO from 203-18-138-91.dyn.cable.fcom.ch[91.138.18.203]: 451 4.7.1 Service unavailable - try again later; proto=SMTP helo=<[192.168.10.10]>

I think there must be something wrong with paths:

Code

root@web4you-server-02:/home/juerg# ls -la /var/spool/postfix/opendkim/opendkim.sock socketls: Zugriff auf '/var/spool/postfix/opendkim/opendkim.sock' nicht möglich: Datei oder Verzeichnis nicht gefundenls: Zugriff auf 'socket' nicht möglich: Datei oder Verzeichnis nicht gefundenroot@web4you-server-02:/home/juerg#

There is a /var/run/opendkim directory with opendkim.pid and opendkim.sock

/etc/opendkim.conf look like:

Code

# This is a basic configuration that can easily be adapted to suit a standard
# installation. For more advanced options, see opendkim.conf(5) and/or
# /usr/share/doc/opendkim/examples/opendkim.conf.sample.
# Log to syslog
Syslog yes
# Required to use local socket with MTAs that access the socket as a non-
# privileged user (e.g. Postfix)
UMask 007
# Sign for example.com with key in /etc/dkimkeys/dkim.key using
# selector '2007' (e.g. 2007._domainkey.example.com)
#Domain example.com
#KeyFile /etc/dkimkeys/dkim.key
#Selector 2007
# Commonly-used options; the commented-out versions show the defaults.
#Canonicalization simple
#Mode sv
#SubDomains no
# Always oversign From (sign using actual From and a null From to prevent
# malicious signatures header fields (From and/or others) between the signer
# and the verifier. From is oversigned by default in the Debian pacakge
# because it is often the identity key used by reputation systems and thus
# somewhat security sensitive.
OversignHeaders From
## ResolverConfiguration filename
## default (none)
##
## Specifies a configuration file to be passed to the Unbound library that
## performs DNS queries applying the DNSSEC protocol. See the Unbound
## documentation at http://unbound.net for the expected content of this file.
## The results of using this and the TrustAnchorFile setting at the same
## time are undefined.
## In Debian, /etc/unbound/unbound.conf is shipped as part of the Suggested
## unbound package
# ResolverConfiguration /etc/unbound/unbound.conf
## TrustAnchorFile filename
## default (none)
##
## Specifies a file from which trust anchor data should be read when doing
## DNS queries and applying the DNSSEC protocol. See the Unbound documentation
## at http://unbound.net for the expected format of this file.
TrustAnchorFile /usr/share/dns/root.key
# Begin Plugin::OpenDKIM
UMask 0111
SyslogSuccess yes
Canonicalization simple
KeyTable refile:/etc/opendkim/KeyTable
SigningTable refile:/etc/opendkim/SigningTable
ExternalIgnoreList /etc/opendkim/TrustedHosts
InternalHosts /etc/opendkim/TrustedHosts
# Ending Plugin::OpenDKIM

Display More

Means access to socket not possible: File or Directory not found.

After completly removing i can send mails.

**Nuxwin** · Jul 10th 2017

Quote from web4you

After upgrade to 4.1.7 (but also in 4.1.6)

Please, stop the bottle

We will investigate for that issue as soon as possible.

**TheCry** · Jul 18th 2017

Hi together,
it seems i had the same problem after a fresh installation.
This is a bug of Debian 9: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864162

You can fix the problem with the following command:

Code

systemctl edit opendkim

Insert the following lines:

Code

[Service]
ExecStart=
ExecStart=/usr/sbin/opendkim -P /var/run/opendkim/opendkim.pid -p local:/var/spool/postfix/opendkim/opendkim.sock

Restart openDKIM and everything will work

**Nuxwin** · Jul 18th 2017

@TheCry

We can always provide our own systemd service file if needed.

However, why an empty ExecStart= ?

**TheCry** · Jul 18th 2017

Quote from Nuxwin

However, why an empty ExecStart= ?

Ups.. Sorry.. This line can be deleted.. My false

**Nuxwin** · Jul 18th 2017

@TheCry

You're welcome.

There is no longer an /etc/default/opendkim file under Stretch for environment variables which we could import in systemd service? Eg, as done in the bug report:

Shell-Script

[Service]
Type=forking
EnvironmentFile=-/etc/default/opendkim
PIDFile=/var/run/opendkim/opendkim.pid
User=opendkim
UMask=0007
ExecStart=/usr/sbin/opendkim -P /var/run/opendkim/opendkim.pid -p $SOCKET
Restart=on-failure
ExecReload=/bin/kill -USR1 $MAINPID

???

My idea is to provide our own systemd service configuration file for opendkim which would be installed in the /etc/systemd/system directory. This would override the default systemd configuration file that is provided by the package.

**TheCry** · Jul 18th 2017

Mhhh.. I'd tested with only one line.. There i got an error

Quote

opendkim.service: Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing.

The empty line must added

**TheCry** · Jul 18th 2017

Quote from Nuxwin

@TheCry

You're welcome.

There is no longer an /etc/default/opendkim file under Stretch for environment variables which we could import in systemd service? Eg, as done in the bug report:
??

The /etc/default/opendkim is still available, but the systemd does not read the file. SO you got the error line in the first post.

**Nuxwin** · Jul 18th 2017

Read my previous answer. You must tell systemd to import the variables from the file as shown above.

**Nuxwin** · Jul 18th 2017

@TheCry

Based on default, could you try with:

/etc/systemd/system/opendkim.service

Code

[Unit]
Description=OpenDKIM DomainKeys Identified Mail (DKIM) Milter
Documentation=man:opendkim(8) man:opendkim.conf(5) man:opendkim-genkey(8) man:opendkim-genzone(8) man:opendkim-testadsp(8) man:opendkim-testkey http://www.opendkim.org/docs.html
After=network.target nss-lookup.target
[Service]
Type=forking
EnvironmentFile=-/etc/default/opendkim
PIDFile=$PIDFILE
User=$USER
Group=$GROUP
UMask=0007
ExecStart=/usr/sbin/opendkim -x /etc/opendkim.conf -u $USER -P $PIDFILE -p $SOCKET
Restart=on-failure
ExecReload=/bin/kill -USR1 $MAINPID
[Install]
WantedBy=multi-user.target

Display More

opendkim Service unavailable

Share

Similar Threads

SpamAssassin reject all mail

opendkim 2.2.0 bloque l'envoi des mails

OpenDKIM 2.0.0 wrong path in postfix main.cf

Opendkim

Debian Stretch - Postfix/Dovecot-SASL - SMTP Fehler (454): Die Authentisierung ist fehlgeschlagen.

Daily visitors