Re: Bad command startup on DNS lookup error for auth socket

2022-09-19 Thread Stefan Foerster
* Matus UHLAR - fantomas : On 18.09.22 14:00, Stefan Foerster wrote: [...] postfix/submission/smtpd[156]: warning: SASL: Connect to Dovecot auth socket 'inet:dovecot:12345' failed: Address not available this looks like "dovecot" host is not resolvable. Yes, that's exactly what happens in

Re: Bad command startup on DNS lookup error for auth socket

2022-09-19 Thread Stefan Foerster
* Wietse Venema : postfix/submission/smtpd[156]: fatal: no SASL authentication mechanisms The server needs to announce the SASL mechanisms in the EHLO response. If it cannot reply to EHLO, then I don't see what good it does if we make this a non-fatal error. Ah, right. I hadn't remembered tha

Re: Bad command startup on DNS lookup error for auth socket

2022-09-18 Thread Wietse Venema
Wietse Venema: > Sorry, my initial diagnosis was incorrect. > > Stefan Foerster: > > postfix/submission/smtpd[156]: warning: host or service dovecot:12345 not > > found: Name does not resolve > > postfix/submission/smtpd[156]: warning: SASL: Connect to Dovecot auth > > socket 'inet:dovecot:12345

Re: Bad command startup on DNS lookup error for auth socket

2022-09-18 Thread Wietse Venema
Sorry, my initial diagnosis was incorrect. Stefan Foerster: > postfix/submission/smtpd[156]: warning: host or service dovecot:12345 not > found: Name does not resolve > postfix/submission/smtpd[156]: warning: SASL: Connect to Dovecot auth socket > 'inet:dovecot:12345' failed: Address not availab

Re: Bad command startup on DNS lookup error for auth socket

2022-09-18 Thread Wietse Venema
Stefan Foerster: > Hello world, > > in a containerized setup I noticed a bad command startup if the AUTH > socket is not available (i.e. the container is down): > > $ postconf smtpd_sasl_path > smtpd_sasl_path = inet:dovecot:12345 > > #v+ > postfix/submission/smtpd[156]: connect from > client.

Re: Bad command startup on DNS lookup error for auth socket

2022-09-18 Thread Matus UHLAR - fantomas
On 18.09.22 14:00, Stefan Foerster wrote: in a containerized setup I noticed a bad command startup if the AUTH socket is not available (i.e. the container is down): $ postconf smtpd_sasl_path smtpd_sasl_path = inet:dovecot:12345 #v+ postfix/submission/smtpd[156]: connect from client.example.c

Bad command startup on DNS lookup error for auth socket

2022-09-18 Thread Stefan Foerster
Hello world, in a containerized setup I noticed a bad command startup if the AUTH socket is not available (i.e. the container is down): $ postconf smtpd_sasl_path smtpd_sasl_path = inet:dovecot:12345 #v+ postfix/submission/smtpd[156]: connect from client.example.com[:xxx:xx:::3] post