Answer the question
In order to leave comments, you need to log in
Opendkim won't start [Ubuntu Server 16.04]?
Hey everyone, I'm setting up DKIM signing on Ubuntu Server 16.04 I
ran into a problem when starting the service
systemctl start opendkim.service
Job for opendkim.service failed because the control process exited with error code. See "systemctl status opendkim.service" and "journalctl -xe" for details.
[email protected] ~ # systemctl status opendkim.service
● opendkim.service - DomainKeys Identified Mail (DKIM) Milter
Loaded: loaded (/lib/systemd/system/opendkim.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-01-11 14:33:50 MSK; 1s ago
Docs: 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
Process: 25272 ExecStart=/usr/sbin/opendkim -x /etc/opendkim.conf -u opendkim -P /var/run/opendkim/opendkim.pid -p $SOCKET $DAEMON_OPTS (code=exited, status=78)
Process: 25269 ExecStartPre=/bin/chown opendkim.opendkim /var/run/opendkim (code=exited, status=0/SUCCESS)
Process: 25265 ExecStartPre=/bin/mkdir -p /var/run/opendkim (code=exited, status=0/SUCCESS)
Jan 11 14:33:50 production systemd[1]: Starting DomainKeys Identified Mail (DKIM) Milter...
Jan 11 14:33:50 production opendkim[25272]: opendkim: /etc/opendkim.conf: configuration error at line 1: unrecognized parameter
Jan 11 14:33:50 production systemd[1]: opendkim.service: Control process exited, code=exited status=78
Jan 11 14:33:50 production systemd[1]: Failed to start DomainKeys Identified Mail (DKIM) Milter.
Jan 11 14:33:50 production systemd[1]: opendkim.service: Unit entered failed state.
Jan 11 14:33:50 production systemd[1]: opendkim.service: Failed with result 'exit-code'.
Jan 11 14:34:49 production systemd[1]: Starting DomainKeys Identified Mail (DKIM) Milter...
Jan 11 14:34:49 production opendkim[25354]: opendkim: /etc/opendkim.conf: configuration error at line 1: unrecognized parameter
Jan 11 14:34:49 production systemd[1]: opendkim.service: Control process exited, code=exited status=78
Jan 11 14:34:49 production systemd[1]: Failed to start DomainKeys Identified Mail (DKIM) Milter.
Jan 11 14:34:49 production systemd[1]: opendkim.service: Unit entered failed state.
Jan 11 14:34:49 production systemd[1]: opendkim.service: Failed with result 'exit-code'.
Syslog yes
UMask 002
Mode sv
OversignHeaders From
AutoRestart Yes
AutoRestartRate 10/1h
PidFile /var/run/opendkim/opendkim.pid
Canonicalization relaxed/relaxed
SyslogSuccess yes
KeyTable file:/etc/opendkim/keytable
SigningTable file:/etc/opendkim/signingtable
ExternalIgnoreList file:/etc/opendkim/TrustedHosts
InternalHosts file:/etc/opendkim/TrustedHosts
SoftwareHeader yes
LogWhy yes
UserID opendkim:opendkim
# Command-line options specified here will override the contents of
# /etc/opendkim.conf. See opendkim(8) for a complete list of options.
#DAEMON_OPTS=""
#
# Uncomment to specify an alternate socket
# Note that setting this will override any Socket value in opendkim.conf
# default:
SOCKET="local:/var/run/opendkim/opendkim.sock"
# listen on all interfaces on port 54321:
#SOCKET="inet:54321"
# listen on loopback on port 12345:
#SOCKET="inet:[email protected]"
# listen on 192.0.2.1 on port 12345:
#SOCKET="inet:[email protected]"
opendkim: OpenDKIM Filter v2.10.3
Compiled with OpenSSL 1.0.2g 1 Mar 2016
SMFI_VERSION 0x1000001
libmilter version 1.0.1
Supported signing algorithms:
rsa-sha1
rsa-sha256
Supported canonicalization algorithms:
relaxed
simple
Active code options:
QUERY_CACHE
USE_DB
USE_LDAP
USE_LUA
USE_ODBX
USE_UNBOUND
_FFR_ATPS
_FFR_RBL
_FFR_REPLACE_RULES
_FFR_STATS
_FFR_VBR
libopendkim 2.10.3: atps query_cache
Answer the question
In order to leave comments, you need to log in
I guess right now. Config in UTF-8, at the beginning of the file byte order mark?
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question