[Dovecot] How to find an invalid configuration in dovecot.conf
Hi,
I'm trying to test Dovecot as an IMAP ans POP3 server but I ran into a fatal problem. On the client side (telnet) I'm trying very basic IMAP commands :
$ telnet localhost imap Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'.
- OK Dovecot ready. 1 LOGIN lavande secret 1 OK Logged in. Connection closed by foreign host.
The login succeeds but the connection hangs !
On the server side it complains that the configuration file dovecot.conf is invalid (it was copied from dovecot-example.conf) but it never tells what line number is incorrect. dovecot -a or dovecot -n doesn't complain about a syntax error or something.
It works for POP3 for the same user/pass.
# /opt/dovecot/sbin/dovecot -F -c /etc/dovecot.conf dovecot: Nov 28 15:43:42 Info: Dovecot v1.0.8 starting up dovecot: Nov 28 15:43:53 Info: imap-login: Login: user=<lavande>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Nov 28 15:43:53 Error: IMAP(lavande): Error: Dovecot is already running with PID 4369 (read from /opt/dovecot-1.0.8/var/run/dovecot/master.pid) dovecot: Nov 28 15:43:53 Error: IMAP(lavande): Fatal: Invalid configuration in /etc/dovecot.conf dovecot: Nov 28 15:43:53 Error: IMAP(lavande): Fatal: EOF while reading environment from master dovecot: Nov 28 15:43:53 Error: child 4380 (imap) returned error 89
Best regards,
-- Laurent PELLISSIER @ Ecole des Mines d'Alès
On Wed, 2007-11-28 at 16:08 +0100, Laurent PELLISSIER wrote:
dovecot: Nov 28 15:43:53 Error: IMAP(lavande): Error: Dovecot is already running with PID 4369 (read from /opt/dovecot-1.0.8/var/run/dovecot/master.pid) dovecot: Nov 28 15:43:53 Error: IMAP(lavande): Fatal: Invalid configuration in /etc/dovecot.conf dovecot: Nov 28 15:43:53 Error: IMAP(lavande): Fatal: EOF while reading environment from master
These happen only if you're trying to use Dovecot from inetd. Do you really need it? I'd suggest running dovecot directly, it works a lot better and most likely gives better error messages as well.
Timo Sirainen a écrit :
These happen only if you're trying to use Dovecot from inetd. Do you really need it? I'd suggest running dovecot directly, it works a lot better and most likely gives better error messages as well.
I run it (compiled by myself) from the command line in the foreground to try to debug it :
# /opt/dovecot/sbin/dovecot -F -c /etc/dovecot.conf
-- Laurent PELLISSIER @ Ecole des Mines d'Alès
On Wed, 2007-11-28 at 16:30 +0100, Laurent PELLISSIER wrote:
Timo Sirainen a écrit :
These happen only if you're trying to use Dovecot from inetd. Do you really need it? I'd suggest running dovecot directly, it works a lot better and most likely gives better error messages as well.
I run it (compiled by myself) from the command line in the foreground to try to debug it :
# /opt/dovecot/sbin/dovecot -F -c /etc/dovecot.conf
What if you try to connect to imap port without running it? Does it give connection refused? Because that error message really looks like you've configured Dovecot to start from inetd.
participants (2)
-
Laurent PELLISSIER
-
Timo Sirainen