Re: AW: Postfix 3.4.14 - Dovecot SASL - strange/buggy behavior in combination with compatibility_level

2021-08-10 Thread Wietse Venema
Podskubka, Stefan: > Wietse Venema: > > The error happened because the hostname "dovecot" did not resolve. > > > > This may be affected by how compatibility_level is set, because > > compatibility_level is processed before Postfix's chroot feature makes some > > files inaccessible. > > Wow, I

AW: Postfix 3.4.14 - Dovecot SASL - strange/buggy behavior in combination with compatibility_level

2021-08-10 Thread Podskubka, Stefan
Wietse Venema: > The error happened because the hostname "dovecot" did not resolve. > > This may be affected by how compatibility_level is set, because > compatibility_level is processed before Postfix's chroot feature makes some > files inaccessible. Wow, I was completely thrown off the right

Re: Postfix 3.4.14 - Dovecot SASL - strange/buggy behavior in combination with compatibility_level

2021-08-10 Thread Wietse Venema
Podskubka, Stefan: > Aug 10 19:39:14 4097ff109d16 postfix/smtpd[112]: > xsasl_dovecot_server_connect: Connecting > Aug 10 19:39:14 4097ff109d16 postfix/smtpd[112]: fatal: host/service > dovecot/666 not found: Device or resource busy This error message is from inet_connect(): if ((parse_err

Postfix 3.4.14 - Dovecot SASL - strange/buggy behavior in combination with compatibility_level

2021-08-10 Thread Podskubka, Stefan
Dear Postfix experts! Although I have found a solution/workaround for the problem mentioned here, for what it's worth, I still wanted to make the effort to report it as a possible bug. Summary === I have a test setup on my local machine where I am running Postfix and Dovecot, each in a