> This does look like a bug in Twisted. Could you file a ticket for it?
Done. #3644.
>
> In the mean time, you can work around this by using a simpler cancel
> technique. Get rid of the "conn.disconnect()" call in cancel and
> instead call the protocol's transport's loseConnection method in f1
Investigating further, I found this is not SSL related problem, but in
my code may have bug. In the following script, I expect that reactor
stops in 2 secs after it started, but connectionLost() is not fired at
all.
Is this a bug in Twisted? Or Am I missing something?
===
Hello,
I'm writing a smtp-client application with twisted.mail. Testing the
application, I noticed that timeout doesn't work in some case if
client started starttls session. If smtp-server stops responding
after DATA command was sent from client, calling
transport.loseConnection() doesn't close
