[issue23906] poplib maxline behaviour may be wrong

2015-08-12 Thread R. David Murray
R. David Murray added the comment: If maxline is too small, messages won't get through. If maxline is too large *huge* messages will get through...and the DDOS danger of exhausting the server's resources will occur. So, we really ought to provide a way to limit the maximum message size

[issue23906] poplib maxline behaviour may be wrong

2015-08-12 Thread shiyao.ma
shiyao.ma added the comment: Instead of setting a MAXSIZE for the email body, rasing up the MAXLINE might be more meaningful. Consider the case of MAXSIZE, it's essentially the same as MAXLINE. If MAXSIZE is relatively small, some messages won't pass through. If the MAXSIZE is relatively

[issue23906] poplib maxline behaviour may be wrong

2015-08-12 Thread R. David Murray
R. David Murray added the comment: Note that the max message size solution can be applied to the maintenance releases as a fix for this issue by choosing a suitable large default message size. The 'feature' part is just the part exposing the size limit in the library API...that part is a

[issue23906] poplib maxline behaviour may be wrong

2015-07-24 Thread Chris Smowton
Chris Smowton added the comment: Created #24706 to describe the unflushed connection problem. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23906 ___

[issue23906] poplib maxline behaviour may be wrong

2015-07-24 Thread Chris Smowton
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 you replied, any

[issue23906] poplib maxline behaviour may be wrong

2015-07-24 Thread R. David Murray
R. David Murray added the comment: Sorry, I was unclear. In order to implement maximum message size we have to do a bit more to the logic than just use the max message size as the readline limit. But it does seem like the right approach to me. --

[issue23906] poplib maxline behaviour may be wrong

2015-07-14 Thread Chris Smowton
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 that's

[issue23906] poplib maxline behaviour may be wrong

2015-07-14 Thread R. David Murray
R. David Murray added the comment: Could you open a separate bug for the recovery problem, please? Using a maximum message size would not solve this problem, but it would give the library user control of when it failed, so it is a good feature request. --

[issue23906] poplib maxline behaviour may be wrong

2015-06-28 Thread Ingo Ruhnke
Ingo Ruhnke added the comment: This also breaks mail retrieval from both gmx.de and gmail.com (two rather large and popular mail provider). After setting _MAXLINE in/usr/lib/python2.7/poplib.py to some arbitrary higher number mail retrieval from both services worked fine again. This this

[issue23906] poplib maxline behaviour may be wrong

2015-06-28 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- versions: +Python 3.4, Python 3.5, Python 3.6 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23906 ___

[issue23906] poplib maxline behaviour may be wrong

2015-06-28 Thread R. David Murray
R. David Murray added the comment: The RFC is in fact not clear on this point. It is entirely possible to read it as saying that each line of a mulitline response is limited to 512 octets. I agree, however, that that is not the most reasonable interpretation. Instead, the line length of

[issue23906] poplib maxline behaviour may be wrong

2015-05-28 Thread Remy Blank
Changes by Remy Blank remy.bl...@pobox.com: -- nosy: +rblank ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23906 ___ ___ Python-bugs-list mailing