[Dovecot] dovecot 2.0beta3 installation
Hello,
I tried to install dovecot 2.0 beta3 and deliver seems to look for its config file in unusual places. In my exim logs, I get: 010-03-17 13:39:24 [31257] 1NrsWt-0004T0-1K email@example.com: dovecot_delivery transport output: lda: Fatal: User lookup failed: net_connect_unix(/opt/dovecot/etc/dovecot/dovecot.conf) failed: No such file or directory 2010-03-17 13:39:24 [31257] 1NrsWt-0004T0-1K == email@example.com (email@example.com) email@example.com R=local_user T=dovecot_delivery defer (0): Child process of dovecot_delivery transport returned 75 (could mean temporary error) from command: /opt/dovecot/libexec/dovecot/deliver
Dovecot have been started with the following command: /opt/dovecot/sbin/dovecot -F -c /etc/dovecot/dovecot2.conf Furthermore, it has been compiled with: --prefix=/opt/dovecot --sysconfdir=/etc I don't see why it searches for /opt/dovecot/etc/dovecot/dovecot.conf
Also, I didn't really find out how to convert the v1.2 config snippet: auth default { mechanisms = digest-md5 cram-md5 ntlm login plain passdb passwd-file { args = /etc/cram.pwd } userdb passwd { } userdb passwd-file { args = /etc/passwd } socket listen { client { path = /var/run/dovecot/auth-client mode = 0666 } } user = exim }
I tried the following, but it does not seem to work as I get an authentication socket protocol error
service auth { unix_listener /var/run/dovecot/auth-client { mode = 0666 } }
Thanks for you help
On 17/03/10 21:11, Timo Sirainen wrote:
On Wed, 2010-03-17 at 21:09 +0100, Renaud Allard wrote:
dovecot_delivery transport output: lda: Fatal: User lookup failed: net_connect_unix(/opt/dovecot/etc/dovecot/dovecot.conf) failed: No such file or directory
Yeah, I broke this yesterday. Fixed it today.
Thanks Timo, so I suppose the daily snapshot should be better for me.
Any idea on the second part of my mail? I didn't really find out how to convert the v1.2 config snippet: auth default { mechanisms = digest-md5 cram-md5 ntlm login plain passdb passwd-file { args = /etc/cram.pwd } userdb passwd { } userdb passwd-file { args = /etc/passwd } socket listen { client { path = /var/run/dovecot/auth-client mode = 0666 } } user = exim }
I tried the following, but it does not seem to work as I get an authentication socket protocol error
service auth { unix_listener /var/run/dovecot/auth-client { mode = 0666 } }
On Wed, 2010-03-17 at 21:21 +0100, Renaud Allard wrote:
dovecot_delivery transport output: lda: Fatal: User lookup failed: net_connect_unix(/opt/dovecot/etc/dovecot/dovecot.conf) failed: No such file or directory
Yeah, I broke this yesterday. Fixed it today.
Thanks Timo, so I suppose the daily snapshot should be better for me.
So do you mean you really tried beta3 release, not the nightly snapshot / hg version? Because I thought that error didn't happen with beta3.
Any idea on the second part of my mail? I didn't really find out how to convert the v1.2 config snippet:
Recent hg versions convert v1.2 configs to v2.0 configs automatically. That is what it outputs with your config:
auth_mechanisms = digest-md5 cram-md5 ntlm login plain passdb { args = /etc/cram.pwd driver = passwd-file } service auth { unix_listener /var/run/dovecot/auth-client { mode = 0666 } user = exim } userdb { driver = passwd } userdb { args = /etc/passwd driver = passwd-file }
I tried the following, but it does not seem to work as I get an authentication socket protocol error
service auth { unix_listener /var/run/dovecot/auth-client { mode = 0666 } }
I don't really see anything wrong with that..
On 17/03/10 21:25, Timo Sirainen wrote:
Thanks Timo, so I suppose the daily snapshot should be better for me.
So do you mean you really tried beta3 release, not the nightly snapshot / hg version? Because I thought that error didn't happen with beta3.
Yes, I really tried beta3 I am also using sieve in dovecot-2-0-pigeonhole-35a382739679, maybe this is the culprit?
Recent hg versions convert v1.2 configs to v2.0 configs automatically.
That's really a nice feature I must admit.
service auth { unix_listener /var/run/dovecot/auth-client { mode = 0666 } }
I don't really see anything wrong with that..
Neither do I (except maybe for the user), hence my question.
On 17/03/10 21:25, Timo Sirainen wrote:
Recent hg versions convert v1.2 configs to v2.0 configs automatically. That is what it outputs with your config:
auth_mechanisms = digest-md5 cram-md5 ntlm login plain passdb { args = /etc/cram.pwd driver = passwd-file } service auth { unix_listener /var/run/dovecot/auth-client { mode = 0666 } user = exim } userdb { driver = passwd } userdb { args = /etc/passwd driver = passwd-file }
I see a difference with what I have configured. My config is: auth_mechanisms = digest-md5 cram-md5 ntlm login plain passdb { driver = passwd-file args = /etc/cram.pwd } userdb { driver = passwd args = /etc/passwd }
Is there really a need for 2 userdb config groups? Reading mails was working fine, only sending was causing problems.
On Wed, 2010-03-17 at 21:45 +0100, Renaud Allard wrote:
userdb { driver = passwd } userdb { args = /etc/passwd driver = passwd-file } .. userdb { driver = passwd args = /etc/passwd }
Is there really a need for 2 userdb config groups?
No, and using /etc/passwd as passwd-file isn't really a good idea either. But you should remove args=/etc/passwd from userdb passwd, it's not needed.
participants (2)
-
Renaud Allard
-
Timo Sirainen