I'm finding it behaves very oddly and has a limited range of clients it
works with, but it's hard to see exactly what's going on because
there's limited debugging available on the box and, well, it's
encrypted. Thunderbird works OK, and I got a good IMAP transcript out
of it, but repeating the same commands with other clients and via
direct connection to the proxy doesn't behave as expected. Here's what
the T-bird log says:
NA:CreateNewLineFromSocket: * OK IMAP4 1.0 server ready^M
NA:SendData: 1 capability^M
-1260471376[9ac5580]: ReadNextLine [stream=96212d0 nb=41 needmore=0]
NA:CreateNewLineFromSocket: * CAPABILITY IMAP4 IMAP4rev1 AUTH=LOGIN^M
-1260471376[9ac5580]: ReadNextLine [stream=96212d0 nb=16 needmore=0]
NA:CreateNewLineFromSocket: 1 OK Completed^M
but here's what happens when I connect with 'openssl s_client -connect
63.209.29.10:993 ' (and with the '-crlf' option which i thought might
help, but doesn't)
* OK IMAP4 1.0 server ready
001 capability
* BAD Argument
read:errno=0
(and the concentrator closes the connection)
This is the same thing that the clients which don't work see. So what's
the difference between the working ones and non-working ones? The same
clients (and s_client) connection directly to the IMAP servers works
fine, so there's definitely something weird going on the proxy.
The only log message emitted here is
06/16/2006 10:27:54.090 SEV=5 EMAILPROXY/47 RPT=3401 x.y.zz.y IMAPS:
Session close.
06/16/2006 10:27:54.090 SEV=4 EMAILPROXY/11 RPT=46 Receive on invalid
connection 0x4.
Any thoughts on what is going wrong here?
