[Dovecot] Not an IMAP4 Server?
I've been testing alpha4, and every once in a while my client
(Thunderbird 1.5 RC1) tells me the dovecot isn't a valid IMAP4 server.
This is usually (maybe always) when I first bring up the client up. If
I just ask the client to get the mail again, it does so happily (without
any errors).
I must say I found dovecot as a pleasant surprise. We have been using UW. Which didn't scale well. I was considering going to cyrus, but dovecot seems to have given much (if not all) of performance improvements without all the hassle of conventing all the existing mbox mail to maildir.
Thanks,
John
-- John Gray gray@agora-net.com AgoraNet, Inc. (302) 224-2475 314 E. Main Street, Suite 1 (302) 224-2552 (fax) Newark, De 19711 http://www.agora-net.com
John Gray wrote:
I've been testing alpha4, and every once in a while my client (Thunderbird 1.5 RC1) tells me the dovecot isn't a valid IMAP4 server. This is usually (maybe always) when I first bring up the client up. If I just ask the client to get the mail again, it does so happily (without any errors).
IIRC, I've encountered that or a similar message (in TB 1.0.6) when the server uses SSL/TLS and the certificate is expired or not trusted, causing Thunderbird to pop up a warning, which gets ignored (since the user is doing something else while Thunderbird starts up) until the connection times out. When the user clicks OK, Thunderbird tries to proceed but the connection is reset, triggering the totally confusing error message.
I don't know if it's it - you should have noticed any such message box, but maybe you didn't think about it. It could also be something similar, with an unexpectedly broken connection in common.
-- Magnus Holmgren
Magnus Holmgren wrote:
John Gray wrote:
I've been testing alpha4, and every once in a while my client (Thunderbird 1.5 RC1) tells me the dovecot isn't a valid IMAP4 server. This is usually (maybe always) when I first bring up the client up. If I just ask the client to get the mail again, it does so happily (without any errors).
IIRC, I've encountered that or a similar message (in TB 1.0.6) when the server uses SSL/TLS and the certificate is expired or not trusted, causing Thunderbird to pop up a warning, which gets ignored (since the user is doing something else while Thunderbird starts up) until the connection times out. When the user clicks OK, Thunderbird tries to proceed but the connection is reset, triggering the totally confusing error message.
I don't know if it's it - you should have noticed any such message box, but maybe you didn't think about it. It could also be something similar, with an unexpectedly broken connection in common.
I'm using with SSL/TLS with not trusted cert. Thanks for the info.
I'll try using my valid cert. If it doesn't happen with that, I'll be
much confident in it.
On another note, I'm testing it on another server using alternate port (994) for TLS, but Thunderbird refuses to connect to it. I wanted to run on alternate port so we can test well before cutting over to it.
Thanks,
John
John Gray wrote:
I've been testing alpha4, and every once in a while my client (Thunderbird 1.5 RC1) tells me the dovecot isn't a valid IMAP4 server. This is usually (maybe always) when I first bring up the client up. If I just ask the client to get the mail again, it does so happily (without any errors).
And there's no problem with other IMAP servers I assume?
--
.-. Mark Rosenstand (-.)
oo| cc )
/'\ (+45) 255 31337 3-n-( (\_;/) mark@borkware.net _(|/->
"JG" == John Gray gray@agora-net.com writes:
JG> I've been testing alpha4, and every once in a while my client
JG> (Thunderbird 1.5 RC1) tells me the dovecot isn't a valid IMAP4
JG> server. This is usually (maybe always) when I first bring up the
JG> client up. If I just ask the client to get the mail again, it
JG> does so happily (without any errors).Clutching at straws but do you have
login_greeting_capability = yes
in dovecot.conf?
I have encountered at least one client that would not talk to dovecot at all without this option because the client wanted to see IMAP4rev1 in the greeting.
Last time I looked I couldn't find any explict requirement for this in the various RFCs though.
participants (4)
-
John Gray
-
Magnus Holmgren
-
Mark Rosenstand
-
pod