[Dovecot] After restart dovecot do not serves IMAPS anymore
I had to restart computer yesterday and now Dovecot has strange behaviour.
Dovecot is running and should serve IMAPS, but client Mozilla Thunderbird cannot connect.
I tried openssl s_client -connect localhost:993 and it said only CONNECTED(00000003).
A time ago when everything was OK, the listing after connection was "a bit" longer than it is now.
I remember there was "OK, dovecot ready" or something like that. Now, there is none.
Of course in /etc/dovecot.conf: protocols = imaps imaps_listen = * ssl_disable = no
So, what's the problem?
Marian Hercek wrote:
I had to restart computer yesterday and now Dovecot has strange behaviour.
Dovecot is running and should serve IMAPS, but client Mozilla Thunderbird cannot connect.
I tried openssl s_client -connect localhost:993 and it said only CONNECTED(00000003).
So, what's the problem?
Any chance you recently upgraded OpenSSL to 0.9.8?
I know it's caused headaches for more than a few people...
-- Curtis Maloney cmaloney@cardgate.net
No, $ openssl version OpenSSL 0.9.7e 25 Oct 2004
And if upgraged to 0.98?
On Tue, 22 Nov 2005, Curtis Maloney wrote:
Marian Hercek wrote:
I had to restart computer yesterday and now Dovecot has strange behaviour.
Dovecot is running and should serve IMAPS, but client Mozilla Thunderbird cannot connect.
I tried openssl s_client -connect localhost:993 and it said only CONNECTED(00000003).
So, what's the problem?
Any chance you recently upgraded OpenSSL to 0.9.8?
I know it's caused headaches for more than a few people...
-- Curtis Maloney cmaloney@cardgate.net
On 22.11.2005, at 08:34, Marian Hercek wrote:
I tried openssl s_client -connect localhost:993 and it said only CONNECTED(00000003).
A time ago when everything was OK, the listing after connection was "a bit" longer than it is now.
I remember there was "OK, dovecot ready" or something like that.
Yea, there should be.
Of course in /etc/dovecot.conf: protocols = imaps imaps_listen = * ssl_disable = no
Looks like it's 0.99.x Dovecot. No idea what the problem is, but I'd suggest upgrading to 1.0alpha. It might have it already fixed, or give better error message (you did check the log if there are any errors?).
Or my other guess would be that something else is listening in port 993, eg. something has added itself to inetd?
participants (3)
-
Curtis Maloney
-
Marian Hercek
-
Timo Sirainen