Brian Pontarelli
2004-07-04 14:01:17 UTC
First off, I'm using mercury server and mozilla client. With Mercury
setup for SSL and using Mozilla and SSL, I either get this error
message from Mercury:
00:37:31.908: Connection from 127.0.0.1, Sun Jul 04 00:37:31 2004<lf>
00:37:31.908: << * OK foo.foo.org IMAP4rev1 Mercury/32 v4.01a server
ready.<cr><lf>
00:37:33.861: >> <cr><lf>
00:37:33.861: << * BAD Malformed command or oversize literal.<cr><lf>
00:37:35.134: >> kk<cr><lf>
00:37:35.144: << * BAD Malformed command or oversize literal.<cr><lf>
I'm using the standard SSL port of 993, but it shouldn't make a
difference. So, then I figured I just have Mozilla not use SSL and
just try secure authentication. Here is the error I get from Mozilla
then:
"You can not login to foo.foo.org because you enabled secure
authentication and this server does not support it."
So, I dug through the list archives and the web and supposedly the
first error (in Mercury) only happens with clients that don't correct
support TLS. Unforntunately Mozilla does and so that rules that out. I
haven't found any help with the second error so far. Has anyone been
able to get this setup working or know for certain it doesn't?
setup for SSL and using Mozilla and SSL, I either get this error
message from Mercury:
00:37:31.908: Connection from 127.0.0.1, Sun Jul 04 00:37:31 2004<lf>
00:37:31.908: << * OK foo.foo.org IMAP4rev1 Mercury/32 v4.01a server
ready.<cr><lf>
00:37:33.861: >> <cr><lf>
00:37:33.861: << * BAD Malformed command or oversize literal.<cr><lf>
00:37:35.134: >> kk<cr><lf>
00:37:35.144: << * BAD Malformed command or oversize literal.<cr><lf>
I'm using the standard SSL port of 993, but it shouldn't make a
difference. So, then I figured I just have Mozilla not use SSL and
just try secure authentication. Here is the error I get from Mozilla
then:
"You can not login to foo.foo.org because you enabled secure
authentication and this server does not support it."
So, I dug through the list archives and the web and supposedly the
first error (in Mercury) only happens with clients that don't correct
support TLS. Unforntunately Mozilla does and so that rules that out. I
haven't found any help with the second error so far. Has anyone been
able to get this setup working or know for certain it doesn't?