On Sun, 2003-02-02 at 08:28, Amelia A.Lewis wrote:
Eventually, I determined what's happening, to some degree. Alas, I've been programming in Java for five years, so I have trouble debugging a real programming language.
Java is real too :)
Adding debugging to client_skip_line (i_info with the contents of data) shows that, after the starttls command, client_skip_line discards the whole next command (in my case, a0002 CAPABILITY). The client is waiting for a response. The server is waiting for a command (having discarded one). login times out sixty seconds later, for inactivity.
Yes, so it seems.
No one else seems to be having this sort of problem, though. Is that because most folks are using TLS on the imaps port? Or have I got a misconfiguration that runs somehow deeper? I don't *think* I'm chasing a wild hare.
I've tested STARTTLS only with Evolution which I guess didn't mind about not getting a reply to next command.
Here's a patch, thanks for bug report :)