[issue21468] NNTPLib connections become corrupt after long periods of activity

Martin Panter added the comment: Perhaps this is similar to Issue 22350 which I just raised. Whenever the NNTP context manager exits, a QUIT command is called, and if the context manager is exiting due to a protocol error or some other exception not handled by the protocol, the code will try a

[issue21468] NNTPLib connections become corrupt after long periods of activity

Changes by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org

[issue21468] NNTPLib connections become corrupt after long periods of activity

James Meneghello added the comment: Yeah, I didn't have a lot of time so I chose just to work around it. When I get a chance I'll have a better look. Good point: I didn't think to try it with SSL off (SSL is enabled for all connections by default with this application). I'll test this and see

[issue21468] NNTPLib connections become corrupt after long periods of activity

R. David Murray added the comment: This is likely to be hard to reproduce (but perhaps someone will try). The best hope of getting it fixed is probably for you to investigate it yourself. Were you using ssl? Also, have you tried all the python versions you selected, and if so, which exact ve

[issue21468] NNTPLib connections become corrupt after long periods of activity

Changes by Terry J. Reedy : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue21468] NNTPLib connections become corrupt after long periods of activity

New submission from James Meneghello: After establishing an NNTP connection for a long-running process (up to hours at a time), the connection will eventually die and start producing infinite random garbage output, a small part of which is seen below. Any subsequent calls to the connection wil