After upgrade to 4.1.7 (but also in 4.1.6) i get the following error in /var/log/mail.log
- 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:
- 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:
- # 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.
