[issue23906] poplib maxline behaviour may be wrong

Chris Smowton added the comment: Created #24706 to describe the unflushed connection problem. -- ___ Python tracker <http://bugs.python.org/issue23906> ___ ___

[issue24706] poplib: Line too long error causes knock-on failure to retrieve all subsequent messages

New submission from Chris Smowton: As mentioned in #23906, when poplib bails from receiving a message with a 'line too long' error it neither flushes nor re-establishes the TCP connection. This means that subsequent commands fail because instead of the expected response we receive p

[issue23906] poplib maxline behaviour may be wrong

Chris Smowton added the comment: Why wouldn't that fix the problem? The issue is poplib not tolerating server behaviour seen in the wild, and if you limit by message size not line length you shouldn't see this problem? (Side note, I'm surprised not to have been emailed when y

[issue16041] poplib: unlimited readline() from connection

Chris Smowton added the comment: +1 to the above; suggest this should be rolled back and replaced with a total message size limit. -- nosy: +Chris Smowton ___ Python tracker <http://bugs.python.org/issue16

[issue23906] poplib maxline behaviour may be wrong

Chris Smowton added the comment: I found the same problem retrieving mail from my ISP's (unknown) POP3 server. I was sent an HTML email as one long 50KB line, which naturally broke everything. Instead of limiting line length, I suggest you should limit total message body size, since t