Marc> I am sure resolving works fine. I tested this in a running mesos
Marc> container, but also in docker run[1]. I need to have the search
Marc> local option in resolve.conf.
Marc> It was actually working, until I started adding the proxy for
Marc> managesieve, but when I reverted, it still do
Thanks ! It did the trick !
We can do very different configurations with this new setting.
Regards,
Sam
Le dim. 24 nov. 2019 à 16:48, Aki Tuomi a
écrit :
> If your dovecot is recent enough you can use mechanisms setting on passdb
> block. See
> https://doc.dovecot.org/configuration_manual/auth
I am sure resolving works fine. I tested this in a running mesos
container, but also in docker run[1]. I need to have the search local
option in resolve.conf.
It was actually working, until I started adding the proxy for
managesieve, but when I reverted, it still does not work. I think the
Marc> I had a working container with dovecot configured as proxy. And
Marc> all of a sudden I am getting these messages 'dovecot: auth:
Marc> Error: DNS lookup for roosit03 failed: Name does not resolve'
Marc> Pinging/nslookup these hostnames is ok
Does nslookup work inside the container? Sound
I had a working container with dovecot configured as proxy. And all of a
sudden I am getting these messages 'dovecot: auth: Error: DNS lookup for
roosit03 failed: Name does not resolve'
Pinging/nslookup these hostnames is ok
