Philipp Tölke added the comment:
The TCP-issues from my post are all resolved. I now know how TCP works; the
behaviour of python seems to be correct.
About the imap-behaviour:
m...@harga ~$ python
Python 2.5.5 (r255:77872, Apr 21 2010, 08:40:04)
[GCC 4.4.3] on linux2
Type "help",
Philipp Tölke added the comment:
The TCP-issues from my post are all resolved. I now know how TCP works; the
behaviour of python seems to be correct.
About the imap-behaviour:
m...@harga ~$ python
Python 2.5.5 (r255:77872, Apr 21 2010, 08:40:04)
[GCC 4.4.3] on linux2
Type "help",
Philipp Tölke added the comment:
Just FYI, this issue is in python2.6, too.
Only, that in 2.6 the GC does not collect the objects immediately, so
that very soon I have a galore of connections in the CLOSE_WAIT-State.
And I checked, I can not read anymore data out of the socket.
Is this a bug
New submission from Philipp Tölke :
While researching some strange logs from out firewall and narrowing it
down to a biff-like imap-client written in python we found the following:
To reproduce:
Start a network-sniffer like wireshark on the loopback-interface
In one shell start some network
