Re: No/Invalid host lookup in smtpd_sasl_path parameter

2017-12-27 Thread Wietse Venema
Lorenzo Bernardi: > It looks like "libnss_dns.so.2" cannot be found due to the chrooted > environment and thus no DNS query can be made (at least for this > specific call). > I fixed it by copying the libraries from /lib/x86_64-linux-gnu/ to > /var/spool/postfix/lib/x86_64-linux-gnu/: > > > cp

Re: No/Invalid host lookup in smtpd_sasl_path parameter

2017-12-27 Thread Lorenzo Bernardi
Thank you Wietse, I followed your advice and ran a strace on the smtpd process. Postfix is running in a chroot environment (/var/spool/postfix) and I noticed the following: Dec 27 16:55:05 85b8d58a343c root: open("/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 18 Dec 27 16:55:05 85b8d58a343c root:

Re: No/Invalid host lookup in smtpd_sasl_path parameter

2017-12-27 Thread Wietse Venema
Lorenzo Bernardi: > Hi Wietse, > > Thank you for your answer. > > The docker containers are running Debian 9.3 and the postfix package > from the official Debian repository (Version: 3.1.6-0+deb9u1). > > As you can see below the source code still contains calls to > gethostbyname(): Grep does

Re: No/Invalid host lookup in smtpd_sasl_path parameter

2017-12-27 Thread Lorenzo Bernardi
Hi Wietse, Thank you for your answer. The docker containers are running Debian 9.3 and the postfix package from the official Debian repository (Version: 3.1.6-0+deb9u1). As you can see below the source code still contains calls to gethostbyname(): postfix-3.1.6~ fgrep gethostbyname . -R -

Re: No/Invalid host lookup in smtpd_sasl_path parameter

2017-12-26 Thread Wietse Venema
Lorenzo Bernardi: > I setup dovecot to handle SASL and listen on port 12345. > When I use the hostname in postfix configuration, I receive the > following error: > postfix/smtpd[141]: fatal: host/service dovecot/12345 not found: No > address associated with hostname The getaddrinfo() SYSTEM LIBR

No/Invalid host lookup in smtpd_sasl_path parameter

2017-12-26 Thread Lorenzo Bernardi
Hi all, I'm currently trying to dockerize my mail server environment and encountered a strange issue on which I spent some time to debug. I have several docker containers running different components: - postfix (172.20.0.4): postfix 3.1.6-0+deb9u1 - dovecot (172.20.0.5): dovecot 1:2.2.27-3+deb9